840D OPCUA en en-US
840D OPCUA en en-US
840D OPCUA en en-US
Preface
Fundamental safety
___________________
instructions 1
SINUMERIK
___________________
SINUMERIK Operate (IM9) 2
SINUMERIK Integrate
___________________
Access MyMachine / OPC UA 3
SINUMERIK 840D sl
Basesoftware and operating SINUMERIK Integrate
___________________
Run MyScreens (BE2) 4
software
___________________
NCU Operating System (IM7) 5
Commissioning Manual
___________________
PCU base software (IM8) 6
___________________
PCU base software (IM10) 7
___________________
Appendix A
Valid for
Control:
SINUMERIK 840D sl/840DE sl
Software:
CNC Software V4.7 SP2
SINUMERIK Operate V4.7 SP2
10/2015
6FC5397-1DP40-5BA3
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
SINUMERIK documentation
The SINUMERIK documentation is organized in the following categories:
● General documentation
● User documentation
● Manufacturer/service documentation
Additional information
You can find information on the following topics at www.siemens.com/motioncontrol/docu:
● Ordering documentation/overview of documentation
● Additional links to download documents
● Using documentation online (find and search in manuals/information)
Please send any questions about the technical documentation (e.g. suggestions for
improvement, corrections) to the following address:
[email protected]
Training
For information about the range of training courses, refer under:
● www.siemens.com/sitrain
SITRAIN - Siemens training for products, systems and solutions in automation technology
● www.siemens.com/sinutrain
SinuTrain - training software for SINUMERIK
FAQs
You can find Frequently Asked Questions in the Service&Support pages under Product
Support. http://support.automation.siemens.com
SINUMERIK
You can find information on SINUMERIK under the following link:
www.siemens.com/sinumerik
Target group
This documentation is intended for commissioning personnel.
The plant or system is readily assembled and wired. For the
following steps, e.g. configuring the individual components,
the Commissioning Manual contains all necessary information or at least references.
Benefits
The intended target group can use the Commissioning Manual to test and commission the
system or the plant correctly and safely.
Utilization phase: Setup and commissioning phase
Standard scope
This documentation only describes the functionality of the standard version. Additions or
revisions made by the machine manufacturer are documented by the machine manufacturer.
Other functions not described in this documentation might be executable in the control. This
does not, however, represent an obligation to supply such functions with a new control or
when servicing.
For the sake of simplicity, this documentation does not contain all detailed information about
all types of the product and cannot cover every conceivable case of installation, operation, or
maintenance.
Technical Support
You will find telephone numbers for other countries for technical support in the Internet under
http://www.siemens.com/automation/service&support
CompactFlash Cards
● Do not remove the memory card while it is being accessed. This can lead to damage of
the memory card and the SINUMERIK as well as the data on the memory card.
● Insert the memory card carefully and the right way round into the memory card slot
(observe indicators such as arrow or similar). This way you avoid mechanical damage to
the memory card or the device.
● Only use memory cards that have been approved by Siemens for use with SINUMERIK.
Even though SINUMERIK follows general industry standards for memory cards, it is
possible that memory cards from some manufacturers will not function perfectly in this
device or are not completely compatible with it (you can obtain information on
compatibility from the memory card manufacturer or supplier).
● For further information on handling CompactFlash cards, please refer to the NCU
manuals.
Preface ................................................................................................................................................... 3
1 Fundamental safety instructions .............................................................................................................. 9
1.1 General safety instructions ....................................................................................................... 9
1.2 Handling electrostatic sensitive devices (ESD) ......................................................................12
1.3 Industrial security ....................................................................................................................13
1.4 Residual risks of power drive systems....................................................................................13
2 SINUMERIK Operate (IM9) ................................................................................................................... 17
3 SINUMERIK Integrate Access MyMachine / OPC UA .......................................................................... 663
4 SINUMERIK Integrate Run MyScreens (BE2) ..................................................................................... 701
5 NCU Operating System (IM7) .............................................................................................................. 973
6 PCU base software (IM8) .................................................................................................................. 1067
7 PCU base software (IM10) ................................................................................................................ 1205
A Appendix........................................................................................................................................... 1363
A.1 Documentation overview ....................................................................................................1363
DANGER
Danger to life due to live parts and other energy sources
Death or serious injury can result when live parts are touched.
• Only work on electrical devices when you are qualified for this job.
• Always observe the country-specific safety rules.
Generally, six steps apply when establishing safety:
1. Prepare for shutdown and notify all those who will be affected by the procedure.
2. Disconnect the machine from the supply.
– Switch off the machine.
– Wait until the discharge time specified on the warning labels has elapsed.
– Check that it really is in a no-voltage condition, from phase conductor to phase
conductor and phase conductor to protective conductor.
– Check whether the existing auxiliary supply circuits are de-energized.
– Ensure that the motors cannot move.
3. Identify all other dangerous energy sources, e.g. compressed air, hydraulic systems, or
water.
4. Isolate or neutralize all hazardous energy sources by closing switches, grounding or
short-circuiting or closing valves, for example.
5. Secure the energy sources against switching on again.
6. Ensure that the correct machine is completely interlocked.
After you have completed the work, restore the operational readiness in the inverse
sequence.
WARNING
Danger to life through a hazardous voltage when connecting an unsuitable power supply
Touching live components can result in death or severe injury.
• Only use power supplies that provide SELV (Safety Extra Low Voltage) or PELV-
(Protective Extra Low Voltage) output voltages for all connections and terminals of the
electronics modules.
WARNING
Danger to life when live parts are touched on damaged devices
Improper handling of devices can cause damage.
For damaged devices, hazardous voltages can be present at the enclosure or at exposed
components; if touched, this can result in death or severe injury.
• Ensure compliance with the limit values specified in the technical data during transport,
storage and operation.
• Do not use any damaged devices.
WARNING
Danger to life through electric shock due to unconnected cable shields
Hazardous touch voltages can occur through capacitive cross-coupling due to unconnected
cable shields.
• As a minimum, connect cable shields and the cores of cables that are not used at one
end at the grounded housing potential.
WARNING
Danger to life due to electric shock when not grounded
For missing or incorrectly implemented protective conductor connection for devices with
protection class I, high voltages can be present at open, exposed parts, which when
touched, can result in death or severe injury.
• Ground the device in compliance with the applicable regulations.
WARNING
Danger to life due to fire spreading if housing is inadequate
Fire and smoke development can cause severe personal injury or material damage.
• Install devices without a protective housing in a metal control cabinet (or protect the
device by another equivalent measure) in such a way that contact with fire is prevented.
• Ensure that smoke can only escape via controlled and monitored paths.
WARNING
Danger to life through unexpected movement of machines when using mobile wireless
devices or mobile phones
Using mobile wireless devices or mobile phones with a transmit power > 1 W closer than
approx. 2 m to the components may cause the devices to malfunction, influence the
functional safety of machines therefore putting people at risk or causing material damage.
• Switch the wireless devices or mobile phones off in the immediate vicinity of the
components.
WARNING
Danger to life due to fire if overheating occurs because of insufficient ventilation clearances
Inadequate ventilation clearances can cause overheating of components with subsequent
fire and smoke. This can cause severe injury or even death. This can also result in
increased downtime and reduced service lives for devices/systems.
• Ensure compliance with the specified minimum clearance as ventilation clearance for
the respective component.
WARNING
Danger to life when safety functions are inactive
Safety functions that are inactive or that have not been adjusted accordingly can cause
operational faults on machines that could lead to serious injury or death.
• Observe the information in the appropriate product documentation before
commissioning.
• Carry out a safety inspection for functions relevant to safety on the entire system,
including all safety-related components.
• Ensure that the safety functions used in your drives and automation tasks are adjusted
and activated through appropriate parameterizing.
• Perform a function test.
• Only put your plant into live operation once you have guaranteed that the functions
relevant to safety are running correctly.
Note
Important safety notices for Safety Integrated functions
If you want to use Safety Integrated functions, you must observe the safety notices in the
Safety Integrated manuals.
WARNING
Danger to life or malfunctions of the machine as a result of incorrect or changed
parameterization
As a result of incorrect or changed parameterization, machines can malfunction, which in
turn can lead to injuries or death.
• Protect the parameterization (parameter assignments) against unauthorized access.
• Respond to possible malfunctions by applying suitable measures (e.g. EMERGENCY
STOP or EMERGENCY OFF).
NOTICE
Damage through electric fields or electrostatic discharge
Electric fields or electrostatic discharge can cause malfunctions through damaged
individual components, integrated circuits, modules or devices.
• Only pack, store, transport and send electronic components, modules or devices in their
original packaging or in other suitable materials, e.g conductive foam rubber of
aluminum foil.
• Only touch components, modules and devices when you are grounded by one of the
following methods:
– Wearing an ESD wrist strap
– Wearing ESD shoes or ESD grounding straps in ESD areas with conductive flooring
• Only place electronic components, modules or devices on conductive surfaces (table
with ESD surface, conductive ESD foam, ESD packaging, ESD transport container).
Note
Industrial security
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, solutions, machines, equipment and/or networks. They are
important components in a holistic industrial security concept. With this in mind, Siemens’
products and solutions undergo continuous development. Siemens recommends strongly
that you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable
preventive action (e.g. cell protection concept) and integrate each component into a holistic,
state-of-the-art industrial security concept. Third-party products that may be in use should
also be considered. For more information about industrial security, visit this address
(http://www.siemens.com/industrialsecurity).
To stay informed about product updates as they occur, sign up for a product-specific
newsletter. For more information, visit this address (http://support.automation.siemens.com).
WARNING
Danger as a result of unsafe operating states resulting from software manipulation
Software manipulation (e.g. by viruses, Trojan horses, malware, worms) can cause unsafe
operating states to develop in your installation which can result in death, severe injuries
and/or material damage.
• Keep the software up to date.
You will find relevant information and newsletters at this address
(http://support.automation.siemens.com).
• Incorporate the automation and drive components into a holistic, state-of-the-art
industrial security concept for the installation or machine.
You will find further information at this address
(http://www.siemens.com/industrialsecurity).
• Make sure that you include all installed products into the holistic industrial security
concept.
The control and drive components of a drive system are approved for industrial and
commercial use in industrial line supplies. Their use in public line supplies requires a
different configuration and/or additional measures.
These components may only be operated in closed housings or in higher-level control
cabinets with protective covers that are closed, and when all of the protective devices are
used.
These components may only be handled by qualified and trained technical personnel who
are knowledgeable and observe all of the safety instructions on the components and in the
associated technical user documentation.
When assessing the machine's risk in accordance with the respective local regulations (e.g.,
EC Machinery Directive), the machine manufacturer must take into account the following
residual risks emanating from the control and drive components of a drive system:
1. Unintentional movements of driven machine components during commissioning,
operation, maintenance, and repairs caused by, for example,
– Hardware and/or software errors in the sensors, control system, actuators, and cables
and connections
– Response times of the control system and of the drive
– Operation and/or environmental conditions outside the specification
– Condensation/conductive contamination
– Parameterization, programming, cabling, and installation errors
– Use of wireless devices/mobile phones in the immediate vicinity of the control system
– External influences/damage
2. In the event of a fault, exceptionally high temperatures, including an open fire, as well as
emissions of light, noise, particles, gases, etc. can occur inside and outside the inverter,
e.g.:
– Component failure
– Software errors
– Operation and/or environmental conditions outside the specification
– External influences/damage
Inverters of the Open Type/IP20 degree of protection must be installed in a metal control
cabinet (or protected by another equivalent measure) such that contact with fire inside
and outside the inverter is not possible.
3. Hazardous shock voltages caused by, for example,
– Component failure
– Influence during electrostatic charging
– Induction of voltages in moving motors
– Operation and/or environmental conditions outside the specification
– Condensation/conductive contamination
– External influences/damage
4. Electrical, magnetic and electromagnetic fields generated in operation that can pose a
risk to people with a pacemaker, implants or metal replacement joints, etc., if they are too
close
5. Release of environmental pollutants or emissions as a result of improper operation of the
system and/or failure to dispose of components safely and correctly
Note
The components must be protected against conductive contamination (e.g. by installing them
in a control cabinet with degree of protection IP54 according to IEC 60529 or NEMA 12).
Assuming that conductive contamination at the installation site can definitely be excluded, a
lower degree of cabinet protection may be permitted.
For more information about residual risks of the components in a drive system, see the
relevant sections in the technical user documentation.
Principles of start-up 2
General settings 3
SINUMERIK
Licensing 4
SINUMERIK 840D sl
SINUMERIK Operate (IM9) 5
Creating drive connections
Channel menu 6
Commissioning Manual
Spindle functions 10
Drive system 11
Tool management 12
Configuring alarms 13
Collision avoidance 14
Valid for
Control:
SINUMERIK 840D sl/840DE sl
Data backup 15
Software:
CNC Software V4.7 SP2
SINUMERIK Operate V4.7 SP2 Configuring the network 16
Configuring cycles 21
Commissioning Manual
Additional language 22
SINUMERIK Operate on PC/
PCU 23
HT 8 24
List of abbreviations/
acronyms A
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 System overview........................................................................................................................................17
1.1 System overview....................................................................................................................17
1.2 System requirements.............................................................................................................18
2 Principles of start-up...................................................................................................................................19
2.1 Data structure of SINUMERIK Operate..................................................................................19
2.2 Editing files.............................................................................................................................22
2.2.1 Editing the file at the controller...............................................................................................22
2.2.2 Editing a file externally...........................................................................................................24
3 General settings.........................................................................................................................................27
3.1 Changing the language..........................................................................................................27
3.2 Set date/time..........................................................................................................................28
3.3 Using the time server.............................................................................................................30
3.4 Configuring Caps Lock...........................................................................................................31
3.5 Activating/deactivating the virtual keyboard...........................................................................31
3.6 Defining the access rights for the "HMI restart" softkey.........................................................32
3.7 Setting the screensaver.........................................................................................................32
3.8 Inserting a user-specific run up screen..................................................................................33
3.9 Access levels ........................................................................................................................33
3.9.1 Definition of access levels......................................................................................................33
3.9.2 Modifying the access levels password...................................................................................34
3.9.3 Access levels for programs....................................................................................................35
3.9.4 Access rights for files.............................................................................................................37
3.9.5 Access levels for softkeys......................................................................................................38
3.9.6 This is how you define new access levels for softkeys..........................................................39
3.10 Program selection..................................................................................................................41
3.10.1 Displaying the softkey............................................................................................................41
4 Licensing....................................................................................................................................................43
4.1 Determining the license requirement.....................................................................................44
4.2 Activating the test license.......................................................................................................46
4.3 Exporting license requirements..............................................................................................47
4.4 Reading in the license key.....................................................................................................47
4.5 Backing up the license of a new CompactFlash card............................................................48
5 Creating drive connections.........................................................................................................................51
5.1 Setting up drives....................................................................................................................51
13.2 Configuring alarm and message texts via alarm text files....................................................227
13.2.1 Creating in-house alarm texts..............................................................................................228
13.2.2 Creating texts for indexed alarm parameters.......................................................................230
13.2.3 Creating part program message texts..................................................................................233
13.2.4 Changing alarm attributes....................................................................................................236
13.2.5 Replacing standard alarm texts............................................................................................240
13.2.6 Range of alarms...................................................................................................................244
13.2.7 Parameter specifications in alarm texts...............................................................................245
13.2.8 Opening error file.................................................................................................................246
13.3 Configuring an alarm log......................................................................................................247
13.3.1 Setting alarm logs from the user interface...........................................................................248
13.3.2 Loading alarm log via configuration file................................................................................248
13.4 PLC alarms with parameters ...............................................................................................252
13.4.1 Definition of a parameter of the octet string data type.........................................................252
13.4.2 Definition of the language-dependent formatting.................................................................255
13.5 Deactivating a warning.........................................................................................................256
14 Collision avoidance...................................................................................................................................259
14.1 Overview..............................................................................................................................259
14.2 General sequence................................................................................................................260
14.3 Set collision avoidance.........................................................................................................261
14.4 Graphic machine model editor.............................................................................................262
14.5 Editing the machine model...................................................................................................263
14.6 Changing and adapting the machine model view................................................................265
14.6.1 Enlarging or reducing the machine graphic..........................................................................265
14.6.2 Changing the section of the machine graphic......................................................................265
14.6.3 Rotating and shifting the machine graphics.........................................................................266
14.6.4 Various machine model views..............................................................................................267
14.6.5 Displaying protection area elements for collision avoidance................................................268
14.7 Creating a kinematic structure.............................................................................................269
14.7.1 Kinematic elements..............................................................................................................269
14.7.1.1 Creating a kinematic chain element.....................................................................................269
14.7.1.2 Kinematic rotation and parallel kinematic rotation................................................................270
14.7.1.3 Linear axis and parallel linear axis.......................................................................................271
14.7.1.4 Rotary axis and parallel rotary axis......................................................................................272
14.7.1.5 Offset and parallel offset......................................................................................................272
14.7.1.6 Switch and parallel switch....................................................................................................273
14.7.2 Protection areas...................................................................................................................273
14.7.2.1 Creating protection areas.....................................................................................................273
14.7.2.2 Tool protection area ............................................................................................................274
14.7.2.3 Machine protection area.......................................................................................................275
14.7.3 Protection area elements.....................................................................................................276
14.7.3.1 Creating protection area elements.......................................................................................276
14.7.3.2 Frame and parallel frame protection area element..............................................................278
14.7.3.3 Box and parallel box protection area elements....................................................................279
14.7.3.4 Sphere and parallel sphere protection area elements.........................................................281
14.7.3.5 Cylinder and parallel cylinder protection area element........................................................282
NCU
The SINUMERIK Operate V4.x operating software is an integral component of the CNC
software V4.x and can therefore run on an NCU 7x0.3. The NCU's CompactFlash card is the
standard data carrier of the CNC software.
The SINUMERIK Operate operating software is started automatically when the NCU software
boots and in the delivery state offers its standard functional scope, which depends on the actual
NC and PLC configuration.
PCU
The SINUMERIK Operate operating software is supplied on DVD and must then be installed
on the hard disk of the PCU. The operating software is automatically started when the controller
boots.
PC
The SINUMERIK Operate operating software is supplied on DVD and can be installed in a
freely selectable directory.
The following sections describe the expansions and adaptations that the machine
manufacturer can make using the SINUMERIK Operate operating software.
References
For a description of the commissioning procedure for the SINUMERIK 840D sl controller,
please refer to the following documentation:
CNC Commissioning Manual: NCK, PLC, Drive
Overview
It is a requirement that all system components be fully mounted, installed and configured.
Commissioning of the NC and PLC must have been completed. The PLC is in the "Run"
condition.
● USB keyboard: Handles text input with upper- and lower-case letters.
● Storage medium, e.g. USB FlashDrive and/or network connection: Handles data exchange
with an external PC/PG.
Note
When you load user data with a USB FlashDrive, the data size must not be larger than 4
GB!
Additional programs
● TextPad text editor: Used for the external creation and editing of XML and INI files in
Windows. The program is available on the Internet at: http://www.textpad.com/
● WinSCP: Enables protected data transfer between different computers (NCU - PC). The
program is available on the Internet at: http://winscp.net/eng/index.php
● RCS Commander: Permits the remote maintenance for machines with the SINUMERIK
Operate operating software from a standard Windows PC.
● As of V4.5, the RCS Commander provides a special conversion function to transfer alarm
texts of HMI Advanced or HMI Embedded to SINUMERIK Operate.
● System Network Center (SNC): Sets up the Ethernet connection of one or more TCUs to
NCU/PCU.
References
A detailed description of the structure and commissioning of the system network with controller
and operator components is provided in the following description:
SINUMERIK 840D sl/840Di sl Operator Components and Networking
Note
The files in the “siemens” directory represent the original status and cannot be modified!
Files, whose contents can be supplemented or modified, are available as templates (specimen
files) in the following directories:
Files Directory
Configuration files /siemens/sinumerik/hmi/template/cfg
Text files /siemens/sinumerik/hmi/template/lng
Before making any changes/supplements, these files should be copied into the /cfg or /lng in /
oem/sinumerik/hmi/, /addon/sinumerik/hmi/ or /user/sinumerik/hmi/ directories.
Structure
The section of the directory structure relevant for SINUMERIK Operate is shown below:
siemens directory
/siemens/sinumerik
/hmi
/appl // applications (operating areas)
/base // basis system components
siemens directory
/cfg // all configuration files
/data // version data
/hlp // online help files
/hlps // online help files, zipped and version files
/ico // symbol files
/Ico640 // icons in resolution 640x480
/ico800 // icons in resolution 800x600
/ico1024 // icons in resolution 1024x768
/ico1280 // icons in resolution 1280x1024
/ico1600 // icons in resolution 1600x1240
/lng // text files
/lngs // text files zipped and versions files
/osal
/ace // ACE/TAO
/qt // Qt
/proj // EasyScreen configuring
/template // various templates
/cfg // templates for configuration files
/ing // templates for text files
/tmpp // storage, temporary data
/sys_cache/hmi // various log files
compat directory
/compat // files for integrating the OEMFrame applications
/add_on
/hmi_adv
/mmc2
/oem
/user
addon directory
/addon/sinumerik
/hmi
/appl // applications (operating areas)
/cfg // configuration files
/data // version data
/hlp // online help files, zipped and version files
/ico // symbol files
/Ico640 // icons in resolution 640x480
/ico800 // icons in resolution 800x600
/ico1024 // icons in resolution 1024x768
addon directory
/ico1280 // icons in resolution 1280x1024
/ico1600 // icons in resolution 1600x1240
/lng // text files
/lngs // text files zipped and versions files
/proj // EasyScreen configuring
/template // various templates
oem directory
/oem/sinumerik
/data // version data
/archive // manufacturer archive
/hmi
/appl // applications (operating areas)
/cfg // configuration files
/data // version data
/hlp // online help files
/hlps // online help files, zipped and version files
/ico // symbol files
/Ico640 // icons in resolution 640x480
/ico800 // icons in resolution 800x600
/ico1024 // icons in resolution 1024x768
/ico1280 // icons in resolution 1280x1024
/ico1600 // icons in resolution 1600x1240
/lng // text files
/lngs // text files zipped and versions files
/proj // EasyScreen configuring
/template // various templates
user directory
/user/sinumerik
/data // version data
/archive // user-specific archive
/prog // user-specific programs
/hmi
/cfg // configuration files
/data // version data
/hlp // online help files
/ico // symbol files
/Ico640 // icons in resolution 640x480
/ico800 // icons in resolution 800x600
/ico1024 // icons in resolution 1024x768
user directory
/ico1280 // icons in resolution 1280x1024
/ico1600 // icons in resolution 1600x1240
/lng // text files
/proj // EasyScreen configuring
/log // log files
/md // machine data views
/proj // EasyScreen configuring
Note
As soon as the file is in the user-specific directory, the entries of this file have priority over the
Siemens file. If an entry is missing in a user-specific file, the corresponding entry from the
Siemens file is used instead.
You need to restart the operating software for the settings made in the file to take effect.
Precondition
● If you copy files, you require access level 1 (manufacturer).
● When assigning a new file name, ensure that only files with a maximum name length of 49
characters can be managed.
6. For instance, on the NCU in the "System CF card" directory, under "oem"
or "user" open the required directory (e.g. /sinumerik/hmi/cfg), in which
the copied file should be saved.
7. Press the "Paste" softkey.
If a file of the same name already exists, you receive a message. You can
overwrite or rename the file.
8. Press the "OK" softkey.
9. You can open the selected file in the editor by pressing the "Open" softkey.
- OR -
Press the <INPUT> key.
- OR -
Double-click the highlighted file.
Rename file
Cut-out/delete file
- OR -
2. Press the ">>" and "Delete" softkeys.
You receive an alarm and you can delete the file by pressing the "OK"
softkey.
Press the "Cancel" softkey to cancel the delete operation.
Example
<!-- Work offset: -->
Note
In the comment itself, you can never use two minus signs one right after the other!
Special characters
If you use characters in the text where the syntax of XML is of significance, then these must
specifically formatted:
Copy file
Using the "WinSCP" or "RCS Commander" program, copy the file from an external computer
to the NCU via a network connection – or in the opposite direction from the NCU to an external
PC.
For a detailed description, see the following sub-book:
References
NCU Operating System (IM7): Backing up and restoring data and WinSCP and PuTTY service
tools
See also
Configuring alarm and message texts via alarm text files (Page 227)
Selecting a language
You can define the language selection mode using the following machine data.
- OR -
Press the "OK" softkey.
The operating software switches to the language selected.
- OR -
Press the "OK" softkey.
During operation, you can switch between the two languages by pressing
the "Change language" softkey.
Format Example
d.M.yy 3.1.09
dd.MM.yy 03.01.09
dd.MM.yyyy 03.01.2009
d/M/yy 3/01/09
dd/MM/yy 03/01/09
dd/MM/yyyy 03/01/2009
M/d/yy 1/3/09
MM/dd/yy 01/03/09
MM/dd/yyyy 01/03/2009
yyyy/MM/dd 2009/01/03
Procedure
5. For SINUMERIK Operate in the NCU: In the entry fields after "new" enter
the actual date and time.
For SINUMERIK Operate on PCU/PC: In the entry fields after "new NCU
+ PCU" enter the actual date and time.
6. Confirm the entry with the "OK" softkey.
The new date and time details are accepted and output in the fields "actual
NCU" and "actual PCU".
Note
You require administrator rights to set the date and time on the PCU/PC.
Note
The setting "Use time server" is not available to SINUMERIK Operate on PCU/PC.
Requirement
You require as a minimum access level 3 (User) to use time servers.
Icon Meaning
The connection status is unknown. The settings have not yet been processed or set.
You are connected to the time server. The system is successfully synchronizing times.
Note
The system checks the time server connection cyclically. If a change is made, it may take a
few seconds for the setting to take effect.
Procedure
Note
If the field "Use time server" is cleared again, the standard "UTC" time zone will apply again.
Setting
MD9009 $MM_KEYBOARD_STATE
=0 CAPSLOCK off (default value)
=2 CAPSLOCK on
Procedure
1. Copy the "slguiconfig.ini" file from the folder
/siemens/sinumerik/hmi/template/cfg.
2. Paste the copy of the file into the following directory:
/oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg.
3. Open the file in the editor.
3.6 Defining the access rights for the "HMI restart" softkey
NOTICE
Influence of screen darkening on the service life
To extend its service life, the recommended duration for darkening a screen is 60 minutes.
If you significantly reduce the duration, i.e. the screen is switched dark too often, this tends
to shorten the screen service life.
Interface signal
The screen is darkened by setting an interface signal.
The following applies when actively darkening the screen using the interface signal:
● It is no longer possible to light up the screen again from the keyboard.
● The first keystroke on the operator panel already triggers an operator action.
Note
In order to prevent accidental operator actions via the interface signal when the screen is
darkened, we recommend disabling the keyboard at the same time.
Overview
You can activate the access levels protected with passwords from the user interface.
The following options are available for editing the passwords:
● Set new password
● Change password
● Delete password
Change password
You must change the standard passwords to obtain a secure access protection.
3. Enter the new password in the input fields "New password" and "Repeat
password".
4. Press the "OK" softkey to confirm your entry.
A new, valid password is only accepted if the two terms entered are
identical.
Delete password
Note
Access authorization is not automatically deleted at POWER ON.
When a general NC reset is performed, the passwords are reset to the default passwords.
Objective
Access levels can be allocated to protect information; they can also be used to prevent
unauthorized operation or deliberate damage to the control system or machine.
With access authorization levels to files and directories, it can be defined as to which users
are authorized to execute which operations on a directory or a file in a file system. Operations
in this sense include:
● Reading the contents of a file (READ), copying the file or placing the file in an archive.
● Changing the contents of a file (WRITE) or deleting the file.
● Executing a file (EXECUTE).
● Listing and displaying a file in a directory (SHOW).
● Creating a file in a directory.
● Displaying or reading the contents of a directory.
● Creating or deleting a directory.
Description of functions
The individual allocation of access rights acts, in the passive NC file system, on the following
directories:
● Part programs
● Subprograms
● Manufacturer cycle directory
Note
Effect of access rights
The more restrictive setting is always effective both when individual access rights have been
allocated and when settings have been made via
MD51050 $MNS_ACCESS_WRITE_PROGRAM.
Example
The paths are composed of the data type identifiers. In the following example, "\wks.dir\*.wpd
\*.mpf" comprises the data type for workpiece directories "wks.dir" the workpieces "*.wpd" and
the part programs "*.mpf".
For all workpieces, 7777 is defined as default setting for new part programs.
All entries are in the section [ACCESSMASKS] and have the following form:
[ACCESSMASKS]
\wks.dir\*.wpd\*.mpf = 7777
\mpf.dir\*.mpf = 6577
\cus.dir\*.spf = 6577
See also
Definition of access levels (Page 33)
Note
Settings for the access rights to directories and files
Via the configuration file and MD51050, access rights of the directories and file types of the
NC memory and user memory (local drive) can be changed and pre-assigned.
Use
The display and operation of softkeys can be suppressed by both the OEM as well as the user.
This allows the operating software to be specifically adapted to the required functional scope
and therefore be configured as transparently as possible.
This means that the functional scope of the system is restricted, to prevent access to functions
in the operating software, or to restrict the possibility of operator errors.
Access hierarchy
A new access level can only be allocated for those softkeys that are also visible and can be
used in the actual access level.
Example: If a softkey is only accessible with the "Manufacturer" access level, then the access
level cannot be changed by an operator with access level "Key-operated switch setting 3".
Restrictions
In order to guarantee that the system remains stable and operable, certain softkeys are
excluded from the access level change, e.g. the "Customize softkeys" softkey itself, in order
that the undo path is not cut-off or the softkey "<< Back" to the vertical softkey bar.
The following softkeys cannot be hidden or the access level changed:
● All "OK" softkeys
● All "Cancel" softkeys
● All "Accept" softkeys
● All "<<" Back and ">>" Continue softkeys
The access level for softkeys in the cycle dialog boxes can also be changed; this does not
apply to softkeys in Easy Screen dialog boxes.
Note
Software upgrade
As all changes of the access levels for softkeys are described using the softkey ID, they still
remain valid after a software upgrade, which may have resulted in softkeys being shifted.
Softkeys, where access is already protected by machine data - for example MD51045
$MNS_ACCESS_TEACH_IN - are only protected by the allocated access level after a new
one has been allocated. The machine data is no longer evaluated.
All of the softkeys hidden using this mechanism can be temporarily displayed again using the
access rights specified by the system. This is done using the "Show all softkeys" softkey. The
softkey is deactivated as long as no softkeys have been allocated new access levels: This
setting remains effective until the system is rebooted.
3.9.6 This is how you define new access levels for softkeys
General sequence
In order to assign a new access level to a softkey, proceed as follows:
● Activate the adaptation mode.
● Change the access level of a softkey.
● Accept the changes and confirm.
Preconditions
Access to the "Customize softkeys" is protected using a general MD51073
$MNS_ACCESS_SET_SOFTKEY_ACCESS. This machine data is pre-assigned access level
3, i.e. the function is available from "Service" password and higher. In order that an operator
with "User" access level can use this function, this machine data should be set to a value > 3.
An external mouse is required in order to make changes.
3. Place the mouse cursor on a softkey and using the right-hand mouse key call the context
menu "Define access level", in order to define a new access level for this softkey.
– The displayed access level is the default setting.
– A softkey is practically made invisible with "Always hide".
– You can reset the additionally allocated access level using "Original setting". This
selection is only listed after an individual access level was set.
4. In order to accept changes, return to the "Start-up" operating area and there, press the
"Close customizing" softkey. This means that you exit the "Customize the softkey access
levels active" mode.
If you acknowledge the following query with "OK", then the changes are accepted and
become effective once the system has rebooted.
5. If the changes to a softkey are not to be applied, select the line and press the "Original
setting" softkey. This means that in the "New access level" column, the "Original setting"
identifier is entered, which functions in the same way as deletion. This entry is no longer
available following a system restart. "
Example
The following access levels were changed:
Once selected, the identifier and position of the softkey are transferred to the "Softkey" column.
Result
When the changes have been accepted, a configuration file with the "slsoftkeyaccess.xml"
name is created and is saved in the file system under the following path: ../user/sinumerik/hmi/
cfg. Files can also be saved in the /oem path, which are evaluated when the system boots.
The following priority applies: oem < user.
Note
Editing the file "slsoftkeyaccess.xml"
In order to avoid errors in the xml syntax and for the softkey identifier the "slsoftkeyaccess.xml"
file may only be edited via the operating software as described above, and not directly in the
file system under "System data". It is possible that the complete file or individual entries for
softkeys can no longer be interpreted.
Configuring a softkey
MD51041 $MNS_ENABLE_PROGLIST_USER
0 No softkey
1 The "Prog. list" softkey is displayed
MD51043 $MNS_ENABLE_PROGLIST_MANUFACT
0 No softkey
1 The "MANUFACTURER" softkey is displayed
Precondition
To create program lists, you require the following authorization:
● "Program manager" operating area: Access level 3 (password: User) or
● "Start-up" operating area: Access level 1 (password: Manufacturer).
Program lists
You can create a program list by combining desired programs from the NC data, e.g.
workpieces, part programs and subprograms. These programs can then be selected by the
PLC for execution.
Procedure
1. Select the "Start-up" operating area if you have the authorization for ac‐
cess level 1 (password: Manufacturer).
- OR -
Select the "Program manager" operating area if you have the authoriza‐
tion for access level 3 (password: User).
2. Press the menu forward key and the "Prog. list" softkey.
The "Program List" window opens.
3. Press the "Manufacturer" softkey if you want to create a program list that
can be used for all machines of a certain series.
4. Place the cursor in the desired line (program number).
5. Press the "Select program" softkey.
The "Programs" window opens. The data tree of the NC memory with the
directories "Workpieces", "Part programs" and "Subprograms" is dis‐
played.
6. Place the cursor on the desired program and press the "OK" softkey.
The selected program is inserted in the first line of the list together with
its path.
- OR -
Enter the program name directly in the list.
If you are making entries manually, check that the path is correct (e.g. //
NC/WKS.DIR/MEINPROGRAMM.WPD/MEINPROGRAMM.MPF).
If required, the extension (.MPF) is added.
Note:
A syntax check is not performed.
With workpieces, make sure that there is a main program or a job list with
the same name in the workpiece itself.
7. To remove a program from the list, place the cursor on the appropriate
line and press the "Delete" softkey.
- OR -
To delete all programs from the program list, press the "Delete all" softkey.
Requirement
If you wish to set or reset the options for a machine, you require at least access level 3 (user).
You can only license options for a machine from this access level and higher.
General information
Serial number of the Com‐ Permanently defined serial number of the CompactFlash card
pactFlash card
Hardware type Data of the control
Machine name/No. Displays the data that is saved in machine data
MD17400 $MN_OEM_GLOBAL_INFO
Only with access level 1 (manufacturer) can a display field be edi‐
ted.
License key Information about options that require a license
Procedure:
License database
The license is purchased from the Web License Manager in the Internet, administered by
Siemens Industry.
For a detailed description, please refer to the following documentation:
References
CNC Commissioning Manual: NCK, PLC, drive
Section "Licensing"
Deactivate options
When importing old archives from other HMI systems, it can occur that options are set which
are no longer required in the actual system – however, these are subject to the license check:
Procedure
1. Press the "All options" softkey to list all the options that can be selected
for this controller.
- OR -
Press the "Missing lic./opt." softkey.
You receive an overview of all options that
● are not adequately licensed
● are licensed, but which were not set
2. Activate or deactivate the required options in the "Set" column:
● Activate the checkbox or
● Enter the number of options
Options shown red are activated, however, not yet licensed or not licensed
in adequate number.
- OR -
Press the "Set option acc. to license" softkey to activate all of the options
contained in the license key.
You obtain a confirmation prompt that you must confirm with "OK".
3. To activate new selected options, press the "Reset (po)" softkey. A safety
prompt appears.
For several options, you will have to also restart SINUMERIK Operate.
Corresponding prompts will appear in the user response line.
4. Press the "OK" softkey to trigger a warm restart.
- OR -
Press the "Cancel" softkey to cancel the process.
Note
If you activate the "Set option acc. to license" function, the sum of the axes that can be activated
may be exceeded. Therefore, reduce the number of actually used axes in the corresponding
options.
Press the "Go to beginning" softkey to start the search at the first option.
Press the "Go to end" softkey to start the search at the last option.
Note
Use of non-licensed options
Before licensing options, you can also activate them temporarily without the license keys and
use them for test purposes. In this case, the control displays alarm 8080/8081 periodically,
indicating that the option used has not yet been assigned the required license. Further, in this
state, the NC cannot be started.
Requirement
If you wish to activate the test license, you require access level 2 (service).
Procedure
Note
In the message line, the control displays the operating time still available for the current test
license period every hour.
Note
Interruption of the test license
A test license period is interrupted in the following cases:
● If no axis is operated actively, e.g. during simulation mode.
● If all non-licensed options are reset.
The test license continues when a non-licensed option is set again.
Note
End of the test license
A test license period is terminated in the following cases:
● If the time has expired.
● If a new valid license key is entered.
No further test license can be activated on the NCU if all test license periods have expired.
Procedure
References
CNC Commissioning Manual: NCK, PLC, drive
Section "Licensing"
Procedure
- OR -
Note:
If several matching .alm files are in the directory, they will be offered to
you in a subsequent selection dialog box.
Select the desired file.
Requirement
To back up the license key, you require a multi-card reader with USB on a PG/PC.
Procedure
1. The CompactFlash card has been inserted into the multi-card reader, which is connected
to the PG/PC.
2. Open directory cards/keys/sinumerik/.
Here you will find the license key in the form of a txt file.
3. Copy the license key to your back-up directory.
4. Insert the CompactFlash Card into the control and perform the restore action.
5. Insert the CompactFlash card into the multi-card reader again.
6. Copy the license key, renamed keys.txt, back to directory cards/keys/sinumerik.
7. Insert the CompactFlash card into the control again.
After the control has been powered up again, the license key will be installed from the file
keys.txt onto the system and be activated. The system renames the txt file to the installation
date.
Software option
In order to use the CompactFlash card as data carrier, you require the "Additional
HMI user memory on CF card of the NCU" option (not for SINUMERIK Operate on
PCU or PC).
Note
The USB interfaces of the NCU are not available for SINUMERIK Operate and therefore cannot
be configured.
References
Operating Manual, Universal/Turning/Milling/Grinding, Chapter "Managing programs" >
"Setting up drives"
File
The created configuration data is stored in the "logdrive.ini" file. This file is located in the /user/
sinumerik/hmi/cfg directory.
General information
Note
We do not recommend that a USB front interface is permitted for part program execution using
EES if a system has several local USB front interfaces (several TCUs, the use of a HT8, etc.).
The connection to the USB FlashDrive can be interrupted as a result of the TCU switchover.
This setting should be made using the checkbox "Use this drive for program execution with
EES".
Note
If a global USB front interface should be used via PCU, then the PCU must be configured as
server via the VNC connection, see Chapter "Configuring VNC connections (Page 323)".
MD9106 $MM_SERVE_EXTCALL_PROGRAMS
=0 HMI ignores EXTCALL instructions and selection via PLC
=1 HMI processes EXTCALL instructions and selection via PLC (default value)
=2 HMI processes EXTCALL instructions and ignores selection via PLC
=3 HMI ignores EXTCALL instructions and processes selection via PLC
Note
A main program selected from an external program memory is selected again automatically
after a power-on if the same program memory is still available and execution of EXTCALL calls
has been activated in MD9106.
Software option
To use this function together with the user memory (100 MB) on the CompactFlash
Card, you require the software option
"CNC extended user memory."
If you also have the option "Additional HMI-Us.memory on CF card of NCU," you can expand
this memory to 6 GB.
Software option
To have unlimited use of this function, you require the software option
"Execution from External Storage (EES)."
Note
The EES function makes EXTCALL calls superfluous. If required, existing EXTCALL calls can
be converted. EXTCALL calls without conversion are also executed for an active EES, although
still as EXTCALL.
References
Function Manual Basic Functions; Mode Group, Channel, Program Operation, Reset
Response (K1)
Chapter "EES (Execution from External Storage)"
Note
The global part program memory plays a role only for the EES function. The creation of a GDIR
is, however, not essential for the EES operation.
Possible procedure
1. Declare the global part program memory in the "Creating drives" window
2. Shift the content of the local program memory with SPF, MPF and WCS directory to an
external drive, e.g. to a USB-FlashDrive.
3. Copy the directories that have been backed up to the global part program memory.
Additional information about managing the program memory is available in the following
documentation:
References
Job Planning Programming Manual, Chapter "File and Program Administration" > "Program
memory"
Q
The channel menu is activated for display via the channel switchover key.
&+$11(/
The channel menu is used to switchover the NC channel displayed in the SINUMERIK Operate
or more precisely at the operator station. If a channel menu has been configured, when the
channel switchover key is pressed, the channel menu for the channel switchover is displayed
to make the appropriate operator action. If there is no channel menu, then the channel
switchover key results in the HMI display advancing to the next NC channel.
Configuring
The configuration is made in the "netnames.ini" file for the operating software, as well as in
the particular "config.ini" files for the individual operator stations.
To configure the data for the operator stations (entries in the "config.ini" files), instead of directly
editing in the "config.ini" file, we recommend that you use the "System Network Center (SNC)"
program.
The "netnames.ini" file must be generated using an editor.
Storage
The "netnames.ini" file is stored for SINUMERIK Operate in the following directory:
/oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg
The "config.ini" file is located in the relevant directory:
● On the NCU:
/user/common/tcu/<TCU name>/common/tcu/config.ini
● On the PCU:
F:\user_base\common\tcu\<TCU name>\common/tcu/config.ini
For <TCU name>, the TCU name of the operator station should be used that was assigned at
the system when a TCU powered-up for the first time. If you work with the "System Network
Center (SNC)" tool, then these file paths are of no significance.
The basic philosophy of the channel menu is to provide - in a selection menu - the operator
with a view of the NC channels of all NCUs that are to be operated with the channel menu. In
conjunction with this, a logical grouping/structuring is introduced using the so-called channel
groups. The desired NC channel can be directly selected using the selection menu. Without
a channel menu, when pressing the channel switchover key, the NC channels must be scrolled
through consecutively until the desired NC channel has been selected. An operator station
can only be switched over across NCUs using the channel menu.
6.2 Constraints
● Only one SINUMERIK Operate on a PCU/ PC may be permanently connected to one NCK.
It is not possible to switch over to another NCK.
● SINUMERIK Operate of an NCU can only operate with its own NCK and cannot be switched
over to another NCU.
Overview
For the channel menu, a logical view is defined across all of the channels of all NCKs involved;
this logical view is structured in channel groups and this in turn in specific NC channels.
A channel group list is defined for the channel menu in order to be able to switch over operation.
A channel group list comprises one or several channel groups. In turn, a channel group
comprises one or several NC channels.
In the channel menu, the channel groups can be selected using the horizontal softkeys.
The channels of a selected channel group can be selected with the vertical softkeys.
A certain NC channel of a specific NCU is always a switchover target that can be selected. A
switchover to another channel triggered via the channel menu can implicitly mean switchover
to another NCU.
&KDQQHOJURXS
OLVW
$VVLJQPHQWIRUKRUL]RQWDO
&KDQQHOJURXS VRIWNH\V
$VVLJQPHQWIRUYHUWLFDO
1&FKDQQHO VRIWNH\V
Note
In a system, for example, a channel group can correspond to a machining station, the channels
contained in it, machining units.
Up to 32 channel groups each with up to 8 channels can be configured in a channel menu.
Two-stage procedure
1. In the first stage, all channel groups that are used in the system are defined in the
"netnames.ini" file, irrespective of the actual operating stations.
2. In the second stage, the version of the channel menu for the specific operating station is
defined in the "config.ini" files belonging to the station.
"netnames.ini" file
A channel group, e.g. channel group 1 is therefore specified as follows:
"config.ini" file
● The data is defined in section [T2M2N].
● The references CH_GRP_xx of the softkeys refer to the channel groups which are defined
in the "netnames.ini" file. This notation is binding.
● SKx in this case, designates the xth horizontal softkey in the channel menu.
Example
...
[T2M2N]
SK1=CH_GRP_1
SK2=CH_GRP_3
SK8=CH_GRP_15
1:N configuration
For a 1:N configuration the following requirements apply:
● A PCU with SINUMERIK Operate can be connected to a maximum of four NCUs.
● SINUMERIK Operate must be switched off on all NCUs.
● The following configuration files must be adapted:
siemens/sinumerik/hmi/template/cfg/netnames.ini
siemens/sinumerik/hmi/template/cfg/mmc.ini
This is illustrated in the following sections using an example with 1 PCU and 2 NCUs.
Example mmc.ini
[Global]
NcddeMachineNames=net, NCU840D_1, NCU840D_2
NcddeDefaultMachineName=NCU840D_1
[NCU840D_1]
ADDRESS0=192.168.214.1,LINE=14,NAME=/NC,SAP=040d,PROFILE=CLT1__CP_L4_INT
ADDRESS1=192.168.214.1,LINE=14,NAME=/PLC,SAP=0202,PROFILE=CLT1__CP_L4_INT
ADDRESS2=192.168.214.1,LINE=14,NAME=/CP,SAP=0502,PROFILE=CLT1__CP_L4_INT
ADDRESS10=192.168.214.1,LINE=14,NAME=/DRIVE_00_000,SAP=0201,
SUBNET=0046-00000000:000,PROFILE=CLT1__CP_L4_INT
ADDRESS11=192.168.214.1,LINE=14,NAME=/DRIVE_03_003,SAP=0900,
PROFILE=CLT1__CP_L4_INT
[NCU840D_2]
ADDRESS0=192.168.214.2,LINE=14,NAME=/NC,SAP=040d,
PROFILE=CLT1__CP_L4_INT
ADDRESS1=192.168.214.2,LINE=14,NAME=/PLC,SAP=0202,
PROFILE=CLT1__CP_L4_INT
ADDRESS2=192.168.214.2,LINE=14,NAME=/CP,SAP=0502,
PROFILE=CLT1__CP_L4_INT
ADDRESS10=192.168.214.2,LINE=14,NAME=/DRIVE_00_000,SAP=0201,
SUBNET=0000-00000000:000,PROFILE=CLT1__CP_L4_INT
ADDRESS11=192.168.214.2,LINE=14,NAME=/DRIVE_03_003,SAP=0900,
PROFILE=CLT1__CP_L4_INT
Example netnames.ini
;******************************************************************
; netnames.ini - EXAMPLE -
;
; This is an example of a netnames.ini for 1:N NCU-switching in
; a configuration of 3 NCU and a PCU50.
;*******************************************************************
[own]
owner = HMI
;***************************
; ChanMenu
;***************************
[chan HMI]
ShowChanMenu = true
;*******************************************************************
;Channel-groups
;Correlation from channel-group to horizontal softkeys
; -> see config.ini of the TCU
;The section [T2M2N] can also be created in the netnames.ini file
;instead of config.ini file. This configuration applies to all TCU,
;which are not configured by their config.ini.
;*******************************************************************
[T2M2N]
SK1 = CH_GRP_1
SK2 = CH_GRP_2
[CH_GRP_1]
Text = 1. NCU
Member1.Target = 192.168.214.241.192.168.214.1.#1
Member1.Text = NCU1%nKanal 1
Member2.Target = 192.168.214.241.192.168.214.1.#2
Member2.Text = NCU1%nKanal 2
[CH_GRP_2]
Text = 2. NCU
Member1.Target = 192.168.214.241.192.168.214.2.#1
Member1.Text = NCU2%nKanal 1
Member2.Target = 192.168.214.241.192.168.214.2.#2
Member2.Text = NCU2%nKanal 2
Note
For switching over an MCP with the operating software, the PLC block FB9 must not be used
(FB9 must not be active). If necessary, the MCP must be switched over in the PLC user
program.
Solution
In the OB100 (call for FB1), set MCP1BusAdr to 255 and MCP1Stop to "true".
In the OB1, scan the "MMCBTSSready" (DB10.DBX108.3) signal. If this is set, write the MCP
address from DB19.DBB123 (MCP index) to the DB7.DBB27 before removing the MCP stop
bit DB7.DBX62.1. The MCP is now active.
If the "MMCBTSSready" (DB10.DBX108.3) is removed again (operating software switches to
another NCU), the MCP stop bit DB7.DBX62.1 will have to be reset.
Sequence:
1. If a distributed job list is active during the selection, all distributed programs on the NCU
are deleted without confirmation. If the workpiece on the NCUs is empty, it will be deleted
there.
2. The programs are copied to the corresponding workpieces of the relevant NCU.
3. Existing programs are overwritten without any message.
4. Following a change in a distributed program on the local drive, the modified programs using
the Editor are copied to the corresponding NCU.
Sample structure
Supplementary conditions
Special behavior:
● Distributed programs are retained during a restart of the operating software.
● On the local drive, distributed programs can neither be deleted nor renamed nor overwritten
using copy/move.
● Changes of distributed programs on the NCU are lost, if they are not manually saved.
● The program correction in the machine is not offered.
● When creating a commissioning archive, all data of the local drive is also automatically
saved.
Restrictions:
● In the event of changes of distributed programs on the local drive using the Editor, it should
be noted that only the channel states are monitored on the NCU currently connected. If the
program is still interrupted or active on another NCU, it cannot be correctly distributed after
the change.
● The display of the active block, the marking of the block search as well as the read-only
handling of the program opened in the Editor are executed only for the active programs of
the currently connected NCU.
● In the Editor, programs are always opened in the context of the currently connected NCU.
This can lead to a faulty step recognition with distributed programs.
● In the current block display in the "Machine" operating area, you can display only the active/
distributed programs of the currently connected NCU.
● The simulation of job lists via several machines is not possible.
● If distributeJoblist=true is configured in the systemconfiguration.ini file, then part
or subprograms can no longer be selected via the "Program Manager" operating area.
Overview
References
You can find a detailed description of the machine and setting data in the following
documentation:
Machine Data and Parameters List Manual
WARNING
Incorrect parameterization
Changes in the machine data have a considerable influence on the machine. Incorrect
configuration of the parameters can endanger human life and cause damage to the
machine.
Note
If the machine data does not use units, the corresponding column is empty. If the data is not
available, the hash symbol "#" is displayed instead of the value. If the value ends in an "H", it
is a hexadecimal value.
The physical units of machine data are displayed on the right-hand side of the input field.
For each machine data item, an activation type can be read in the column on the right.
Additional Information
In the footer you are given a brief explanation of the selected machine or setting data item.
Procedure
2. Press the "Mach. data" softkey. Additional softkeys for the individual ma‐
chine data areas are displayed.
3. Press the "General MD", "Channel MD", or "Axis MD" softkey.
The window opens and the selected machine data is displayed.
- OR -
Press the "Reset (po)" softkey.
A safety prompt appears.
7. Press the "OK" softkey to trigger a warm restart.
- OR -
Press the "Cancel" softkey if you do not want to apply the settings.
Axis selection
If several components are available for the area selected (e.g. "Axis MD"), you can choose
from the following options:
- OR -
Press the "Direct selection..." softkey.
The "Axis Direct Selection" window opens.
2. Select the required axis directly from those available in the drop-down list
box.
- OR -
Press the "Cancel" softkey to reject the settings.
Procedure
- OR -
Press the "Cancel" softkey if you do not want to apply the settings.
Procedure
5. Place the cursor on the desired setting data and position the cursor on
the entry to be changed. Enter the desired value.
6. Depending on the activation type, there are two ways of activating the
settings:
Press the "Activate MD (cf)" softkey.
- OR -
Press the "Reset (po)" softkey.
A safety prompt appears.
7. Press the "OK" softkey to trigger a warm restart.
- OR -
Press the "Cancel" softkey if you do not want to apply the settings.
Axis/channel selection
If several components are available for the area selected (e.g. "Axis SD" or "Channel SD"),
you can choose from the following options:
1. Press the "Axis +" or "Axis -" or "Channel +" or "Channel -" softkey.
The values of the next (+) and the previous axis/channel (-) are displayed.
- OR -
Press the "Direct selection..." softkey.
The "Direct Selection" window opens.
2. Select the required axis directly from those available in the drop-down list
box.
3. Press the "OK" softkey to save the setting.
- OR -
Press the "Cancel" softkey to reject the setting.
Precondition
Settings for drive parameters are protected with access level 2 (service).
The lists of the drive parameters are visible with access level 4 (keyswitch 3).
Please refer to the following documentation for information on commissioning the drive:
References
CNC Commissioning Manual: NCK, PLC, drives
Procedure
Extended reset
If you wish to carry out a warm restart only for specific objects or specific areas, then additional
softkeys are available for this purpose.
All of the control units and the NCK in the system are restarted. This
softkey corresponds to the "Reset (po)" softkey if you confirm the prompt
with "Yes".
All of the control units and the NCK in the system as well as the operator
software are restarted.
Filter options
It is possible to limit the machine data display using the following filtering methods:
● Only display axes that are used
● According to indices
● According to display groups
● Display expert parameters
Display groups
A display group contains machine data within a machine data area that belongs to the same
topic.
Note
To find out which display group a machine data item belongs to, refer to the "Display filter"
parameter associated with the description of the machine data element in question.
References: List Manual (book 1)
Select/deselect display groups to increase or decrease the number of machine data items
displayed for the current machine data area.
Procedure
- OR -
Press the "Deselect all" softkey.
All checkmarks are removed and you can select individual display groups.
Press the "OK" softkey to save the settings.
Procedure
2. Press the "Mach. data" softkey and select the required machine data area
(e.g. general machine data).
5. If you activate the "Display all bits" checkbox, all bits regardless of their
data type (8, 16 or 32 bits) are displayed. Activate the relevant bit.
6. Press the "OK" softkey. The setting is checked and an error message may
be output.
The window closes and you return to the machine data overview.
The new value is displayed in hexadecimal format.
Note
BICO values can also be entered by copying and inserting or also directly entered the field.
Procedure
3. Press the "Control unit MD" softkey and select a BICO parameter, e.g.
"p738".
4. Position the cursor on the entry to be changed, e.g. BICO 63.2091.0
5. Press the <SELECT> or <INSERT> key.
The "BICO Editor" window opens.
Note
The BICO editor also opens if you enter a value other than 0 or 1 for the value to be changed.
Procedure
3. Select the desired drive parameter area, e.g. "Control unit MD".
4. Select the desired parameter, e.g. "p3" and position the cursor at the entry
to be changed, e.g. "[1] Display, Si...".
5. Press the <SELECT> or <INSERT> key.
A window containing a list of all defined enum values and their descrip‐
tions opens.
Search strategies
● When a digit or a digit with an index is entered, an exact search for this parameter is
performed.
Example: If "9" is entered > p9 will be found (but not p99)
● When text is entered, a full-text search is performed: i.e. the term is sought in the relevant
table and in the explanations in the footers.
Note
Search with place holders
When searching for machine data, you have the option of using place holders:
● "*": Replaces any character string
● "?": Replaces any character
Searched fields
A search is made in the following fields of the machine data for the character string that has
been entered if the "Additionally search in the explanation texts" option is not set:
● Machine data number
● Symbolic name
● Unit
The following fields are additionally searched if the "Additionally search in the explanation
texts" option is set:
● Descriptive text
● Bit texts
● Enum texts (only for drives)
Procedure
The cursor is positioned on the first entry that corresponds to the search
term.
7. Press the "Continue search" softkey if this machine, setting or display
machine data item is not the one you are looking for.
Press the "Go to start" softkey to start the search at the first data.
Press the "Go to end" softkey to start the search at the last data.
Overview
The "Manage data" function is used to simplify the commissioning and permits the transfer,
backup, loading and comparing of machine, setting, compensation and drive data at the file
level. The files are saved in the .tea ASCII format.
The "Manage data" softkey is visible as of access level "Service" (= 2).
The following option fields are available in the "Transfer Machine Data" window:
● Transfer data within the controller
Only those controller objects are listed that are currently available in the controller.
● Save data to a file
Additional files with the extensions .acx and .log are created for the SINAMICS parameters:
– Files with the extension .acx contain the parameter descriptions for the selected drive
object.
– The log file may also contain the warnings and errors that occurred during the conversion
from .acx to .tea.
● Load data from a file
Note
An NCK and drive reset is only triggered automatically for drive objects after loading. A
reset must be triggered manually for all other controller objects.
● Compare data
Several files (.tea) and/or controller objects (axis, channel, servo, infeed, etc. ) can be
compared at the same time. An online comparison of constantly changing data is not
possible because the values are saved temporarily at the time of the comparison.
Up to eight elements can be taken into the list of the data to be compared.
Procedure
6. In the window that opens, select the target controller object and confirm
with "OK".
Save data to a file
5. Position the cursor on a controller object and confirm with "OK".
6. The "Save Under: Select Archive" window opens and the appropriate
storage location is preselected.
If required, press the "New directory" softkey to generate a new subdir‐
ectory. Enter the required name in the "New Directory" window and con‐
firm with "OK".
7. In the "New File" window, enter the required name for the file to be saved
and confirm with "OK".
The stored files can be found in the data tree of the "System data" in the
HMI data/Data backups/IB data directory.
Load data from a file
5. The "Load Trace: Select File" window opens.
Position the cursor on a .tea file that is located either in the IB data direc‐
tory or on a USB-FlashDrive and confirm with "OK".
Please note: If the source and target drive object numbers differ when
loading drive data, you must adapt individual parameters. To do this,
press the "Adapt" softkey and edit the parameter values in the window
that appears.
Compare data
5. In the "Compare Data - Controller" window, select an element to be com‐
pared from the tree structure of the control objects.
- OR -
Press the "File" softkey to select a .tea file to be compared from the tree
structure of the files.
6. Press the "Add to list" softkey.
The list of the data to be compared is displayed in the lower part of the
window and the selected element is added.
7. Press the "Delete from list" softkey to remove individual elements from
the comparison list.
- OR -
Deactivate the checkbox of the selected element in the list of the data to
be compared.
8. When at least two elements are listed, the "Compare" softkey is enabled.
Press this softkey to perform the comparison.
Use
In the "User Views" window you can create and adapt all machine data relevant to a particular
functionality. Machine data is individually collated to simplify the user's task.
You can include additional comments when creating and/or editing user views.
Note
Importing user views (compatibility)
If you have already created user views in HMI-Advanced, copy the *.klb files to /user/sinumerik/
hmi/template/user_views to use them in SINUMERIK Operate.
Procedure
1. Select the "Start-up" operating area and press the "Mach. data" softkey.
"New view".
The "New View" window opens.
3. Enter the desired view name.
Press the "OK" softkey.
If a user view already exists with the same name, you receive a safety
prompt as to whether the existing view should be overwritten.
4. Press the "Enter data" softkey.
The "Insert data" selection box opens.
5. Open the selection list with the <INSERT> key, select a machine data
area and press the <INPUT> key.
Select a machine data item with the cursor keys or using the "Find"
softkey.
6. Press the "Insert before line" or "Insert after line" softkey to insert the
selected machine data at the required position in the user view.
Note:
You can navigate in the open user view with the mouse and select a
line without closing the list box.
7. Press the "Back" softkey to close the list box and return to the user view
you want to edit.
Your entries are automatically stored.
8. Press the "Insert text" softkey to insert any text in the open user view.
The "Insert Text" input window opens.
9. Enter a text and explanatory description for the text and press the "Insert
before line" or "Insert after line" softkey to accept the text.
10. Press the "Back" softkey to save your entries and return to the user view
you are editing.
You can use the Search dialog box to look for a particular data item.
Procedure
1. Select the "Start-up" operating area and press the "Mach. data" softkey.
3. Press the "Edit view” softkey. Additional softkeys to edit the user view are
listed.
4. Press the "Insert data" softkey if you wish to enter another data item.
- OR -
Press the "Delete line" softkey to remove the selected line from the view.
The data item is removed without a prompt.
- OR -
Press the "Properties" softkey to view the texts for comments and, if re‐
quired, change.
The "Properties" window is opened. For machine data, depending on the
setting, the description or the machine data is displayed in the lower left-
hand window.
7. Press the "Back" softkey to save your changes.
You can use the Search dialog box to look for a particular data item.
Press the "Go to start" softkey to start the search at the first entry.
Press the "Go to end" softkey to start the search at the last entry.
Press the "Continue search" softkey if the data found during the search
does not match up with what you are looking for.
Procedure
With the final confirmation prompt you will be requested to confirm with
either "Yes" or cancel with "No".
or
The "User views" dialog is then redisplayed.
Just like before, as an alternative, it is possible to delete a user view under "System data"
under the following path: ../user/sinumerik/hmi/template/user_views
Files
For "xxx" the specified language code must be used, e.g. "deu" for German, "eng" for English,
etc.
Supported languages (Page 612)
Ensure that the file names are written in lower case letters.
Procedure
1. Depending on the machine or setting data for which you wish to change the plain text,
create the corresponding file, e.g. "nctea_xxx.txt".
2. Save the file with the UTF-8 coding in order that umlauts and special characters are
correctly displayed in SINUMERIK Operate.
3. Place the file in SINUMERIK Operate in the following directory:
System CF card/user/sinumerik/hmi/Ing or
System CF card/oem/sinumerik/hmi/Ing or
System CF card/addon/sinumerik/hmi/Ing
Note
The files are searched through in the sequence of the directories "user", "oem" and "addon".
The first file that is found is evaluated. If, e.g. text files are available in the "user" and "oem"
directories, the files are evaluated in the "user" directory.
Note
If a machine data item has different indices and you do not specify an index for the plain text,
the same plain text appears for all the indices of the machine data item.
The parameters and indices must be sorted in an ascending order.
OEM-specific logo
The Siemens logo is visible in the header of the "Machine" operating area.
You can replace the Siemens logo with your own logo.
Procedure:
1. Name your own logo "logo.png".
Note
The file name must not contain any lower case letters.
2. Save your own logo depending on the bitmap size, in one of the directories: /oem/sinumerik/
hmi/ico or /user/sinumerik/hmi/ico
Section Meaning
Selected G groups This area is intended for operation of the controller in Siemens mode.
Selected G groups ISO This area is intended for operation of the controller in ISO mode.
mode
SelectedGGroupN = M
N Position where G-code group M will be displayed.
If you want to leave a position empty, omit the number (M), e.g. "SelectedGGroup1 = "
M The number of the G-code group to be displayed at position N
[Selected G-Groups]
SelectedGGroup1 = 1
SelectedGGroup2 = 2
SelectedGGroup3 = 3
SelectedGGroup4 = 4
SelectedGGroup5 = 5
SelectedGGroup6 = 6
SelectedGGroup7 = 7
SelectedGGroup8 = 8
SelectedGGroup9 = 9
SelectedGGroup10 = 11
SelectedGGroup12 = 12
SelectedGGroup13 = 13
SelectedGGroup14 = 14
SelectedGGroup15 = 15
SelectedGGroup16 = 16
[Selected G-Groups ISO-Mode]
... (as with section for Siemens)
Procedure
1. Copy the "slmagcodeconfig.ini" file from the folder
/siemens/sinumerik/hmi/template/cfg.
2. Place the file in the following directory: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg.
As soon as the file is located in the user-specific directory, the entries for this file take
precedence over the Siemens file. If an entry is missing in a user-specific file, the
corresponding entry from the Siemens file is used instead.
3. Open the file and enter the number of the G code in question at the required position
"SelectedGGroup1 = 5".
I.e. the 5th G code group will be displayed at the 1st position.
Overview
The channel operational messages are displayed in the third line of the header in the "Machine"
operating area. There are two types of channel operational messages:
1. Channel operational messages that require an operator action to continue a program, e.g.
feed enable missing, M01 active.
The channel operational messages are identified by exclamation marks.
2. Channel operational messages that do not require an operator action to continue a program.
A stop condition is active for a length of time (>1 s) and is interrupted by the program
processing, e.g. dwell time active, waiting for tool change.
The channel operational message is identified by a clock icon and disappears after a certain
time.
File
The settings for this are specified in the "slmahdconfig.ini" file.
Section Meaning
CondStopIcons Specification of an icon that is to be displayed with a certain channel operational
message.
If no icon is specified for a certain channel operational message, then the icon
specified for "DefaultIcon" is displayed.
CondDelayTime Specification of how long (in milliseconds) a certain message must be present
before it is displayed.
● If no time is specified for a certain channel operational message, then the time
specified at "CondDelayTime" is used.
● If the channel operational message is to be displayed immediately, "0" must
be specified as time.
Procedure
1. Copy the "slmahdconfig.ini" file from the /siemens/sinumerik/hmi/template/cfg directory.
2. Place the file in the following directory: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg.
3. Open the file and make the required settings.
"slmahdconfig.ini" file
Standard configuration
[CondStopIcons]
Default icon = condwait.png
1 = condstop.png ; No NC ready
2 = condstop.png ; No mode group ready
3 = condstop.png ; EMERGENCY STOP active
4 = condstop.png ; Alarm with stop active
5 = condstop.png ; M0/M1 active
6 = condstop.png ; Block in SBL mode terminated
7 = condstop.png ; NC stop active
8 = condstop.png ; Read-in enable missing
9 = condstop.png ; Feed enable missing
10 = condwait.png ; Dwell time active
11 = condwait.png ; Aux. function acknowledgment missing
12 = condstop.png ; Axis enable missing
13 = condwait.png ; Exact stop not reached
[CondDelayTime]
Default delay time = 1000
1 = 0 ; No NC ready
2 = 0 ; No mode group ready
3 = 0 ; EMERGENCY STOP active
4 = 0 ; Alarm with stop active
5 = 0 ; M0/M1 active
6 = 0 ; Block in SBL mode terminated
7 = 0 ; NC stop active
8 = 0 ; Read-in enable missing
References
Function Manual, Basic Functions, Mode Group, Channel, Program Operation, Reset Behavior
(K1)
Activate TEACH IN
The TEACH IN function is activated in part via the general configuration machine data.
Settings
MD51034 $MNS_TEACH_MODE
Bit 0 = 1 The "Teach progr." softkey is displayed. The approached position is accepted into the
program with the "Accept" softkey, default value.
Bit 1 = 1 The acceptance of the teach-in block can be blocked by the PLC.
DB19.DBX13.0 = 0 Block is accepted
DB19.DBX13.0 = 1 Block is not accepted
Activating TEACH IN
1. Set the machine data and initiate a reset.
2. Now change into the "AUTO" and "MDA" operating mode.
3. Select the TEACH IN machine function.
4. Press the "Teach prog." softkey.
MD51032 $MNS_STAT_DISPLAY_BASE Number base for display of the joint position STAT
=2 Binary display, joint position STAT (standard)
The following machine data have a similar effect, but it is channel-specific effect in this case:
MD52032 $MCS_STAT_DISPLAY_BASE Number base for display of the joint position STAT
=0 Value from MD51032 effective
If the value from MD52032 is > 0, MD51032 is ignored for this channel.
If the value from MD52033 is > 0, MD51033 is ignored for this channel.
The possible input values (values > 0) in MD52032 and MD52033 correspond to MD51032
and MD51033.
For further information about STAT and TU, please refer to the following documentation:
References
Extended Functions Function Manual; Kinematic Transformation (M1)
Section "Cartesian PTP travel."
The following machine data can be used to set the possible variants for the block search in a
JobShop program (ShopMill, ShopTurn):
Note
The "Block search mode" softkey is only displayed, if, in the machine data MD51024 or
MD51028, more than one version for the block search has been defined; for example "Block
search with calculation without approach" and "Block search with calculation with approach".
When so doing, take into account that the search versions set active in the "Block search
mode" window are also referred to the program.
Settings
If you activate the "Skip EXCALL" function, then you must set the following general
configuration machine data:
For an external main program, a block search without calculation is always a fast block search.
Only the blocks from the search position are loaded.
Using the multi-channel editor, for a multi-channel machine, you can open, change or generate
programs simultaneously that are independent of one another from a time perspective. In this
case, the programs involved are displayed next to one another in the editor.
Further, you have the option of simulating the programs before they are actually processed at
your control.
In addition, you can align the programs according to synchronization points.
Precondition
● Multi-channel data only involve machines where the first technology is turning.
● For multi-channel machine, the following data must be the same for all channels:
– Measurement unit
– Work offset (e.g. G54)
– Z value of the work offset (optional)
– Blank
– Speed limitation
● Further, the following JobShop-specific data must be the same for all channels:
– Retraction plane (one each for the main and counterspindle)
– Tailstock (one each for the main and counterspindle)
– Tool change point (one each for the main and counterspindle)
– Safety clearance
– Climbing/ and conventional
Software option
You require the "ShopMill/ShopTurn" option to generate and edit ShopTurn/
ShopMill programs.
After you have created a job list, in the "multi-channel data" parameter screen, you can combine
the data from the G code and JobShop, which is then saved as cycle call in the job list. The
"multi-channel data" parameter screen is displayed as soon as at least one ShopTurn program
is contained in a job list.
General information
"Manual machine" allows you to work with large cycles in manual mode without having to write
programs especially for this purpose.
Software option
You require the following software option in order to use this function:
"ShopMill/ShopTurn"
Activation
Enables
Handwheel
MD11346 $MN_HANDWH_TRUE_DISTANCE = 3 Handwheel path or velocity specifica‐
tion
MD11602 $MN_ASUP_START_MASK bit 0, 3 =1 Ignore stop conditions for ASUB
MD20150 $MC_G_CODE_RESET_VALUE [7] = 2 Delete position of the G groups; run-up
G54 active
MD20624 $MC_HANDWH_CHAN_STOP_COND = 0xFFFF Definition of the behavior of traveling
with handwheel, channel-specific
MD32084 HANDWH_STOP_COND = 0x7FF Behavior, handwheel travel
MD52212 FUNCTION_MASK_TECH Bit 9 = 1 Function screen form across technolo‐
gies; work offset via softkey
Note
If, in machine data MD52212 FUNCTION_MASK_TECH bit 9 is set, the "WO selection" softkey
is displayed in the "Work Offset – G54 … G599" window.
Note
If $MC_GCODE_RESET_VALUES[59] = 2 is set in the MD20150 machine data, the "Limit
stops" softkey is displayed in the "Manual Machine" window. This requires that
$MC_MM_NUM_WORKAREA_CS_GROUPS also has the value 1 for MD28600.
Feedrate
SD42600 $SC_JOG_FEED_PER_REV_SOURCE = -3 Revolutional feedrate control in JOG
mode
SD43300 $SA_ASSIGN_FEED_PER_REV_SOURCE [X ax‐ Revolutional feedrate for positioning
is] = -3 axis X
SD43300 $SA_ASSIGN_FEED_PER_REV_SOURCE [Z ax‐ Revolutional feedrate for positioning
is] = -3 axis Z
Note
Ensure that the axis-specific setting data SD43300 SA_ASSIGN_FEED_PER_REV_SOURCE
are set the same.
References
● Operating:
Operating Manual, Turning/Milling, Chapter "Working with a manual machine"
● Programming:
Programming Manual, Fundamentals; Chapter "Working area limit"
Function
User icons can be displayed in the Machine operating area in the second line in the header.
In this case, the program name is displayed in the right-hand field of the third line in the header.
Active hold conditions hide the program name.
The display of the user icons is controlled via PLC bits. The icons are provided in the form of
PNG files and stored resolution-specifically in the file system at: /user/sinumerik/hmi/
ico/ico640, etc. Maximum 16 positions are available in the header to display the user icons.
Configuration
The user icons are configured in the slmahdconfig.ini file in Section [UserIcons]. The
following data is required:
● The start address of the PLC double word with the bits to control the display of the user
icons.
● For each bit used, the file name of the icon and the position at which the icon should be
displayed.
Alternatively, you can use the following parameters for the definition:
● USER_ICON_BASE
This means that 32 bits are available with UI_0 (highest bit) to UI_31 (lowest bit).
Example: USER_ICON_BASE=DB80.DBB0
⇒ UI_0 = DB80DBX3.0 and UI_31 = DB80.DBX0.7
● USER_ICON_BASE256
This means that 256 bits are available with UI_0 (highest bit) to UI_255 (lowest bit).
Example: USER_ICON_BASE256=DB19.DBB80
⇒ UI_0 = DB19.DBX111.0 and UI_255 = DB19.DBX80.7
Example
[UserIcons]
USER_ICON_BASE=DB19.DBB80
; set the start byte of the PLC double word that displays the icons (DB19.DBD80)
UI_0 = icon1.png,4
; show icon1.png on position 4 if bit 0 (DB19.DBX83.0) is set
UI_1 = icon2.png,6
; show icon2.png on position 6 if bit 1 (DB19.DBX83.1) is set
Superimposition
With a non-unique selection (bits for multiple identifiers whose image is to be displayed at the
same position):
The image with the lower identifier number is superimposed with the image with the higher
identifier number for the same position. Non-unique selection can also be used with less than
16 active selection bits. The PLC can deliberately use this superimposition to overlay less
important displays (with lower identifier numbers) with important displays (high identifier
numbers).
Note
If two HMI applications are assigned to one NC/PLC unit (M:N), the PLC must first determine
from the interface which of the HMI interfaces is active. Icons can be requested by the PLC
for the active HMI application only.
Possible applications
With a unique selection, a maximum of 16 bits are set simultaneously in the four selection
bytes for each of the different positions.
● 32 alternative images for a position, each selected with a different bit (currently only one
active selection bit)
● Two alternative images for each of the permissible 16 positions, each position requires two
of the 32 selection bits (maximum 16 active selection bits at any one time)
● Combination thereof with a maximum total of 32 images for the maximum 16 positions
(maximum of 16 active selection bits at any one time)
● More than 16 selection bits.
[OEMTextInfo]
OEM_NUMBER_TEXTFIELD = 1 ; maximum of 3 text fields per line
OEM_TEXT_BASE = DBx.DBBy
The interface in the user DB has the following format:
The first parameter contains an offset for a text number with a base of 700,000 (user PLC
texts). If this parameter = 0, the corresponding line is deleted. The second parameter contains
a maximum 12-character string. Unless empty, this text is output instead of the user PLC text.
The parameters must be written from "back to front" in the PLC, i.e. all parameters must be
initialized before the first byte is set. The data for the next line is located exactly 18 bytes after
the start byte. The lines are output from left to right; a maximum of three output fields per line
are provided (i.e. a total of six fields are possible).
A hotlink to the first byte for each line is set up in the operating software. If a change occurs
in that byte, the operating software responds. If the operating software displayed the data, it
writes a -1 to the first variable. The operating software is informed about this change by means
of the hotlink, whereupon it writes a 0 to this variable.
The HMI itself does not have to react to this change. The PLC can only write data to the
interface again if the variable is set to 0. This mechanism ensures that the operating software
knows about all parameter changes.
[OemIcons]
OI_0= <name.png>, <position>
...
OI_31= <name.png>, <position>
Here, <name> is the file name of the bit map and <Position> is the output position (from 1 to
16) in the display line. Multiple bit maps can be output at the same position. If more than one
bit map is active simultaneously at the same position, the bit map with the highest screen
number is displayed.
The output is controlled by means of a PLC double word. This double word is declared in the
next section in the HEADER.INI file:
[OemIcons]
Oem_ICON_BASE = DBx.DBBy
Each bit in this double word represents exactly one OEM icon corresponding to the screen
number. Thus, if bit 0 is set, bit map OI_0 is displayed. If a bit is reset, the associated bit map
is deleted.
A maximum of 16 icons can be displayed, enabling a total of 16 display positions. Empty
positions need not be specified.
You will find additional information about making these settings in the following document:
References
Universal/Turning/Milling/Grinding Operating Manual
● Section "Machining a workpiece" > "Settings for Automatic mode mode"
● Section "Machining a workpiece" > "Editing a program" > "Settings for the editor"
Note
Machine data MD18370, MD18371, and MD28302 are still valid for machining time recording
when they are assigned higher values.
Software option
You require the "3D simulation 1 (finished part)" option
for the 3D representation of the simulation.
Simulation is supported with its own program interpreter (SNCK) and a separate simulation-
data environment in SINUMERIK Operate. The SNCK considers the complete syntax of the
SINUMERIK control family, including the possibility of incorporating special user options on
the machine by comparing data with the NC environment. The simulation data can be matched
statically as required with the NC environment (initialization data, macros, user data, tool data,
machining cycles) or also dynamically when tool data or machining cycles are changed.
Machining simulations, with emphasis on the drilling, milling, turning and grinding technologies,
can be performed in the workpiece coordinate system for certain machine kinematics on the
user interface of the controller:
● The simulation of the finished part is performed with the real NC data.
● The NC data is automatically compared at each change of the part program.
● The simulation allows a dynamic representation of the machining, even for active 5-axis
transformation (TRAORI) and swiveled planes.
● Turning on milling machines.
● Simulation of a machining channel for conventional milling machines.
● Simulation of up to four machining channels for turning machines with B axis.
● Intelligent determination of the block times and the program execution time.
● Very fast graphical representation through the continuous refinement of the workpiece.
● Optimum resolution for each selected picture area.
● Any sections are possible.
● In parallel to the machining of one workpiece, the machining of another workpiece can be
simulated (as of NCU 720.x).
● 3D representation of simulation (option).
Turning technology
Examples of machine kinematics:
● Conventional turning with two geometry axes
● Three spindles: Main spindle, counterspindle, tool spindle
● Counterspindle slides, tailstock as NC axis
● B axis: Aligning turning tools in the tool spindle
● Milling with geometry axes: TRANSMIT, TRACYL, TRAANG
Machine data for the turning technology:
Milling technology
Examples of machine kinematics:
● Milling with five axes: Swivel/TRAORI
● Swivel head change
Machine data for the milling technology:
Grinding technology
Machine data for the grinding technology:
Enter the direction of rotation for the rotary axes that are not configured in a toolholder or a 5-
axis transformation via the following channel-specific machine data.
The MD52290 $MCS_SIM_DISPLAY_CONFIG machine data acts only on the OP019. It has
no significance for SINUMERIK 828D.
In the channel-specific machine data, for at least one geometry axis per channel, enter a value
other than 0.0, e.g. 0.001. If the value is 0.0, the system assumes that this parameter has still
not been set.
Deactivating simulation
The following machine data must be set to deactivate the simulation:
Software option
You require the option "Simultaneous recording (real-time simulation)"
for the "Simultaneous recording" function.
Software option
You require the "ShopMill/ShopTurn" option to display the tailstock
Software option
You require the "3D simulation 1 (finished part)" option
for the 3D representation of the simultaneous recording function.
During machining, the tool paths can be simultaneously recorded on the display of the
controller in a three-side view or 3D view. Workpiece graphics and views correspond to the
graphic simulation.
Note
To prevent an incomplete representation, you must activate the simultaneous recording prior
to the NC start.
Requirements
● The machine has several clamping options available for selection.
● The machine has a clamping option that does not point in the Z direction as standard (e.g.
a boring mill).
Under the following circumstances, you can specify the position and orientation of the rotary
axes in the machine data MD53220 and MD52207:
● The position and orientation of the rotary axis is offset against the MCS zero point, but not
specified by a tool holder or a TRAORI.
● In a turning machine, the reference points of the main spindle or counterspindle are offset
against the MCS zero point in X or Z.
● The counterspindle cannot be traversed with a saddle, but rather is at a fixed position.
In order that for simulation / simultaneous recording, the rotary axes are displayed at the correct
location, their positions in the machine coordinate system must be specified using the following
machine data:
For further information about the transformation of a rotary axis, see Chapter"Configuring
cycles (Page 465)".
Function
Set the following channel-specific machine data:
Function options
In the program header, a blank can be optionally set to A, B, C and table clamping:
Note
To obtain the selection option in the program header, two rotary axes must be defined for the
raw part clamping.
63 =
<
&
References
Operating Manual, Milling
● Chapter "Create ShopMill program" > "Program header"
● Chapter "Create ShopMill program" > "Change program settings"
End of program
The following M functions are used for the end of program:
Example
MD10714 $MN_M_NO_FCT_EOP = 32 means "M32" for the program end of a program
generated in the "JOG" or "MDA" operating mode.
Among other things, this functionality is required in order to continuously start the spindle in
manual operation (e.g. for scratching).
Configuring keys
If you implement a manual control using the keys on the machine control panel, then this is
realized via the following interface signals in the spindle data block:
Note
If the spindle must be stopped when the program is running, then set the interface signal
DB3x.DBX4.3, "Feed stop/spindle stop" in the user PLC.
Additional settings:
References
For a detailed description how to to configure the spindle, see
Function Manual, Basic Functions; Spindles (S1)
In order that the operating software identifies the spindle as analog spindle, enter the axis
index of the analog spindle in the following machine data:
Procedure
1. Select the "Start-up" operating area and press the "NC" softkey.
- OR -
Press the "Select axis" softkey.
The "Axis Direct Selection" window opens. Position the cursor on the de‐
sired axis and confirm with "OK".
References
Extended Functions Function Manual; Compensations (K3)
Software option
For the "Spindle diagnostics" you require the "S-Monitor" option.
Main spindle drives are monitored via various status signals. The DRIVE-CLiQ connection at
the spindle can be used to evaluate these signals in the drive. The status signals are evaluated
for more effective diagnostics of the spindle operating states. The following information is
displayed on the user interface with the aid of the "S-Monitor" software option:
● Operating hours
● Temperatures
● Speed/torque
● Clamping system
● Logistics data
Requirements
● A spindle has an SMI24 sensor module:
r0459, bit 14 = 1.
● Drive telegram 139 is configured for the spindle.
● The spindle functionality for the machine axis is present, when:
MD35000 $MA_SPIND_ASSIGN_TO_MACHAX > 0
The value corresponds to the spindle number.
References
For further information, please refer to the following documentation:
● Basic Functions (S1), Function Manual; Section "Spindle with SMI24"
● "Start-up a hybrid spindle with SMI24" application description on the Internet at:
Commissioning of a hybrid spindle with SMI 24 (http://support.automation.siemens.com/),
Entry ID 67598396
Data overview
The "S1 Spindle Diagnostics" window shows the following information:
Parameter Value
Operating hours h
● Spindle under control
● Spindle under speed
Number of clamping cycles (tool change)
Definition of a clamping cycle: Released clamping state [3] → Clamped clamping state
[7, 8 or 10] → Released clamping state [3].
Motor temperature °C
Clamping state (sensor 1) V
Piston free (sensor 4)
e.g. defined rotary angular position of the shaft (sensor 5) Yes/No
Maximum speed rpm
Procedure
Note
If several spindles are in operation, select the desired spindle using the "Spindle +" or "Spindle
-" softkey.
10.4.2 Temperatures
Which temperatures are evaluated and displayed depends on the number and the mounting
location (e.g. for sensor S6, bearing temperature front) of the sensors installed in the spindle.
The motor temperature is not displayed when the temperature sensor sensor type parameter
p0601 = 0 or 1.
Note
Temperature limits
The limit values displayed here refer to the spindle monitoring and have no effect on the drive
parameter values set in the drive that apply for the shutdown response of the spindle. The
temperature limit values are preset in the SMI24 and cannot be changed in this window. If
necessary, you must adapt the shutdown limit values for the drive.
Shutdown response
The alarm and fault thresholds of the motor temperature sensor that are displayed on the user
interface as limits, are stored in the SMI24. They are used for the statistical evaluation of the
SMI24 and for the shutdown response of the drive. A delay time setting for the violation of the
alarm threshold stored in the SMI24 until the fault is triggered is not relevant for the display.
Please note: The motor parameter values of p0604, p0605 (alarm/fault threshold) and the
delay time p0606 are predefined and cannot be changed.
The delay time in p0606 has no effect on the values displayed on the user interface. This
means: When the alarm threshold is violated and the delay time set in p0606 has expired, the
"Motor temperature fault" signal does not change the "Last upper limit violation" display value
and the "Number of upper limit violations" is not incremented.
The parameter values of p0604, p0605 (alarm/fault threshold) and p0606 (delay time) have
an effect on the shutdown response of the spindle. The spindle is shut down when the fault
threshold is violated or the alarm threshold is violated and the delay time set in p0603 has
expired.
Currently, the delay time is not predefined by the SMI24. The parameter value of p0603 is set
to the factory setting (240 s).
Alarms:
● 207015 = motor temperature sensor alarm
● 207016 = motor temperature sensor fault
Shutdown response
The alarm and fault thresholds of the additional temperature sensor that are displayed on the
user interface as limits, are stored in the SMI24. They are used only for the statistical evaluation
of the SMI24. A delay time setting for the violation of the alarm threshold stored in the SMI24
until the fault is triggered is not relevant for the display.
Please note: The parameter values of p4102[0..1] (alarm/fault threshold) and p4103 (delay
time) are predefined and cannot be changed.
Changing the parameter values of p4102[0..1] (alarm/fault threshold) and p4103 (delay time)
has no effect on the values displayed on the user interface.
The parameter values of p4102[0..1] (alarm/fault threshold) and p4103 (delay time) have an
effect on the shutdown response of the spindle. The spindle is shut down when the fault
threshold is violated or the alarm threshold is violated and the delay time set in p4103 has
expired. These parameters can be adapted accordingly to prevent an unwanted shutdown of
the spindle.
Currently, the delay time is not predefined by the SMI24. The parameter value of p4103 is set
to the factory setting (0 s). This means: The timer is deactivated.
Alarms:
● 207017 = additional temperature alarm threshold violated
● 207018 = additional temperature fault threshold violated
Color Meaning
Temperature range up to the first limit.
The heights of the individual bar fields correspond to the parameterized temperature ranges
of the relevant temperature measuring point.
The specified times for the individual temperature ranges of a measuring point (sensor) are
the operating hours under speed.
The currently measured temperatures are displayed below the bars.
10.4.6 Speed/torque
To check the loads on the spindle, the speed and the torque are recorded in a histogram as
a function of the operating hours. The color coding indicates the following states:
● Light green: low load
● Green: rated load
● Yellow: high load
● Orange: critical load
The heights of the individual bars correspond to the percentage time shares (dwell time) in
relation to the operating hours under speed. The accumulated number of operating hours under
speed for the spindle are shown above or below the respective bar for the corresponding speed
or torque range. The width of the bar corresponds to the evaluated speed or torque range.
Possible conclusions
● The speed histogram is an indication of the load on the bearings and rotary gland caused
by the speed.
● The speed histogram is an indication of the load on the bearings caused by the stock
removal forces. The relationship between torque and radial force changes depending on
the tool diameter (lever arm), the milling arc (superimposition of the cutting forces of the
individual cutting edges) and the cutting force coefficients (the stock removal force consists
of cutting force, feedrate force and passive force - only the cutting force is acquired via the
torque).
The current state values of the sensors, the tool clamping, the speed setpoint and the active
speed limitation are displayed in the signal overview
References
For information on the associated interface signals (NC → PLC), refer to the following
references:
● NC Variable and Interface Signals List Manual, Section "Axis/spindle-specific signals".
Procedure
You can adapt the preset speed limits to your requirements by pressing the "Change" softkey.
NOTICE
Damage to the spindle through too high a speed
Changes to the preset speed limits can result in safety-relevant changes of the operating
states and to damage on the spindle.
If a Power On of the SMI24 is performed during the start-up phase, the previously determined
values are discarded. The counter for the first 100 clamping operations is set to zero and the
reference times up to the 100th clamping operation can be determined again. After the start-
up phase (first 100 clamping operations), the values of the reference clamping time are
"frozen". Even after a Power On of the SMI24, the values remain stored and can no longer be
changed.
Requirement
The spindle characteristics can only be read out with the "Service" access level.
Spindle characteristics
The following spindle manufacturer characteristics can be read out via DRIVE-CLiQ:
● Manufacturer's identifier
● Drawing number
● Serial number
● Date of manufacture
● Service date and service information (1...4):
The service information corresponds to the reference number for the service report from
the WEISS Spindeltechnologie GmbH company.
Procedure
Once commissioning of the PLC has been completed, you can carry out commissioning of the
SINAMICS drives via the user interface of SINUMERIK Operate.
References
The procedure for commissioning the SINAMICS drives is described in the following
documentation:
CNC Commissioning Manual: NCK, PLC, drive
MD19320 $ON_TECHNO_FUNCTION_MASK
=2000000H
Bit 25 Enables the tool monitoring function without magazine management.
MD19320 $ON_TECHNO_FUNCTION_MASK
= 10H
Bit 4 Enables the tool monitoring function with magazine management.
The access level of individual parameters can be overlaid through settings in the
<PARAMETERCONFIGURATION> tag, "Access level" entry (see SectionConfiguring list
parameters (Page 161)).
Additional settings
You can enable further functions on the user interface via the following machine data / setting
data:
MD52270 $MCS_TM_FUNCTION_MASK
Bit 0 Creating a tool at the magazine location is not permitted.
Bit 1 Load/unload lock if the machine is not in the reset state.
Bit 2 Load/unload lock for EMERGENCY OFF.
Bit 3 Loading/unloading or relocating tool in/out of spindle locked.
Bit 4 Tool loaded directly into spindle.
Bit 5 Using the grinding configuration file.
Bit 6 Relocating a tool in/out of spindle is permitted despite lock (see bit 3).
Bit 7 Tool is created using the number.
Bit 8 Hide tool relocation.
Bit 9 Hide magazine positioning.
Bit 10 Reactivate tool with magazine positioning.
Bit 11 Reactivate tool in all monitoring types.
Bit 12 Hide reactivating tool.
SD54215 $SNS_TM_FUNCTION_MASK_SET
Bit 0 Diameter display for rotating tools.
Cutting edge parameters 6 (tool nose radius) and 15 (wear radius) are not displayed as a
radius value, but as a diameter value for the following tool types: Types 100 to 299, 580,
710, 711, 712, 713, 714 and 725.
Cutting edge parameter 7 (outside radius) is not displayed as a radius value, but as a diam‐
eter value for the following tool types: Types 140 and 714.
Bit 1 M4 is the standard direction of rotation for all turning tools. When creating turning tools, the
direction of rotation is pre-assigned with M4.
Bit 2 A name is not suggested when creating a tool.
Bit 3 Input lock, tool name and tool type for loaded tools. For loaded tools, the tool name and the
tool type can no longer be changed.
Bit 4 Input lock for loaded tools if the channel is not in the reset state.
Bit 5 Tool wear entries are added: Wear data is entered in addition to the already existing wear
value.
Bit 6 Only numerical entries are permitted in the "Tool identifier".
Bit 7 Hide tool monitoring parameters. The tool monitoring parameters are hidden in the user
interface.
Bit 8 Diameter display for face axis - geometry. The geometry value of the transverse axis is
displayed as a diameter value, if a transverse axis is defined in MD20100 $DIAME‐
TER_AX_DEF and SD42940 $TOOL_LENGTH_CONST is set to 18 and SD42950
$TOOL_LENGTH_TYPE is set to 2.
Bit 9 Diameter display for face axis - wear. The wear value of the transverse axis is displayed as
a diameter value, if a transverse axis is defined in MD20100 $DIAMETER_AX_DEF and
SD42940 $TOOL_LENGTH_CONST is set to 18 and SD42950 $TOOL_LENGTH_TYPE is
set to 2.
Bit 10 Enable tool load/relocate to buffer storage locations. The magazine number can be entered
into the load dialog box. It is therefore possible to access the buffer storage via magazine
number 9998.
Bit 11 Creating new tools at gripper locations is blocked.
Bit 12 Measuring tools are not unloaded with the "Unload all" function.
Bit 13 The wear value is not deleted when a tool geometry value is entered.
Bit 14 Load or relocate tool. Empty location search performed without default value with the tool
magazine last used.
= 0 Empty location always starts with the tool magazine last used.
= 1: Empty location search follows the set search strategy.
Dependencies
The setting data SD54215 $TM_FUNCTION_MASK_SET and the machine data MD20360
$TOOL_PARAMETER_DEF_MASK have the following dependencies:
Note
If, in machine data MD22562 $MC_TOOL_CHANGE_ERROR_MODE bit 2 = 1, then you have
the option, using a correction selection (D No.) in the program, to stop the machine until the
PLC signals that the tool change has been completed. To do this, machine data MD20270
$MC_CUTTING_EDGE_DEFAULT must be set to = 0.
Configurable settings
The following settings can be configured:
● General settings
● Configure the tool lists
● Configure the list parameters
● Configure the tool types
● Configure the "Additional Data" window
● Configure the "New Tool - Favorites" window
● Configure the "New Tool" window
● Configuring the "New Multitool" window
● Configuring the "New Tool from Code Carrier" window
● Configuring the "New Tool from File" window
● Configure the default values for new tools
● Configure the "Details" window
● Assign names for magazines and magazine locations
● Configuring the "Assign Tooltips for Multitool Locations" window
● Assign names for magazine location types
● Assignment of magazines and magazine locations to channels
● Assignment of magazines to coordinate systems
● Disabling the softkey depending on filters
Procedure
1. Open the directory: /siemens/sinumerik/hmi/template/cfg.
2. Copy the "oem_sltmlistconfig.xml" template file
3. Copy the file to the directory /oem/sinumerik/hmi/cfg
OR: /user/sinumerik/hmi/cfg.
4. Change the file name according to the set technology:
5. Remove the comments of the example in the template to create your specific configuration.
Configuration examples
Examples for all possible configurations are provided in the template oem_sltmlistconfig.xml,
which are described individually in the following sections:
Configuration examples
<SETTINGS> tag
The general settings for the tool management user interface are stored in the <SETTINGS>
tag.
Entries Meaning
ReactivateWithMagPos True - reactivate with positioning of the tool to the tool mag‐
azine loading point.
False - default setting, reactivate without positioning the tool
magazine.
ReactivateAllMonitorModes True - the actual values of all the monitoring types set in the
NC are reset.
False - default setting, actual value of the active monitoring
type is reset.
ReactivateEnabled True - default setting, reactivation is enabled.
False - reactivation is disabled.
CreateNewToolDialog True - the "New Tool" window is displayed. In this window,
you can specify the tool name and the size of the tool (over‐
sized tool) before actually creating the tool. Other input op‐
tions can be defined by configuring the "New tool" window.
False - default setting, the "New Tool" window is not dis‐
played. Once the name has been entered, the tool will be
created directly in the tool list.
CreateNewMultiToolDialog True - default setting, the "New Multitool" window is dis‐
played. In this window, you can configure the following be‐
fore actually creating the multitool:
● Multitool names
● Number of multitool locations
● Type of clearance input
● Value of the location clearance for each multitool location
False - the "New Multitool" window is not displayed. Once
the name has been entered, the multitool will be created
directly in the tool list.
MagazineSelectionDialog True - a dialog box displaying the buffer, tool magazine and
NC memory is displayed. A mark can be added to or re‐
moved from each of these elements to indicate whether that
element appears in the list display. The "Go to" softkey can
be used to select an element directly in the list display.
False - no dialog box for magazine selection. The system
switches between the buffer, the tool magazines and the
NC memory.
If there is no MagazineSelectionDialog entry in the
<Settings> tag, the dialog box is automatically displayed
with more than one tool magazine (excluding the system
magazine) when magazine configuration is taking place. If
there is only one tool magazine, the switchover function is
used.
Entries Meaning
NewToolFavoritesOnly Refers to the "New tool" function.
True - only those tool types that are configured as favorites
are listed.
False - default setting, all tool types are listed.
SortationInFirstEtcLevel True - the "Sorting" function is placed at the first softkey
level. The "Continue" function is omitted.
False - default setting, sorting at all softkey levels.
ToolBufferOnceOnTop True - default setting, buffer is displayed at the start of the
list.
False - buffer is displayed for each magazine. Only those
locations are displayed that are assigned to the magazine.
UnloadToolFromLoadPlaceEnabled True - a tool at the load station can be removed from the
load station using the "Unload" softkey.
False - default setting. The "Unload" softkey is not displayed
for a tool at the load position.
CreateNewToolWithCuttPos9Enabled True - cutting edge position 9 is offered in the cutting edge
position selection.
True - default setting, cutting edge position 9 is not offered
in the cutting edge position selection.
AutoHNumberDisplayEnabled Column of the cutting edge parameter "IsoHNoDPH - ISO
H number" depending on the machine configuration.
True - default setting, the column is automatically displayed.
False - the column is not automatically displayed.
AutoUniqueDNumberDisplayEnabled Column of the cutting edge parameter "UniqueDNo" de‐
pending on the machine configuration.
True - default setting, the column is automatically displayed.
False - the column is not automatically displayed.
AccessLevelDeleteAllDNos The following entry specifies the access level as of which
the "Delete all D numbers delete" function is offered.
Default setting: Access level 3 (user) - relevant only when
the "Unique D number" setting has been made.
MagazineNumberOfDCheckAndActivate Default setting: -2 - the tools of all magazines are considered
by the function "Check for unique D number and activate
tool."
>0 - The above function only considers the tools of the
named magazine.
AutoFixedPlaceDisplayEnabled Column of the tool parameter "ToolStateFixed" - tool status
- tool is fixed-location coded and acts dependent on the
magazine configuration.
True - default setting, the column is automatically hidden, if
all of the configured magazines are fixed location coded.
False - the column is not automatically hidden.
MagPlaceAdapterDisplayEnabled Columns of the magazine location adapter parameters are
displayed in the "Magazine" window.
False - default setting, parameters are not displayed.
Entries Meaning
AdaptTransDataViewEnabled The magazine location adapter transformed display of the
cutting edge parameters is enabled. It can be switched on
and off in the settings dialog of the tool lists.
False - default setting, the magazine location adapter trans‐
formed display of the cutting edge parameters is not ena‐
bled.
ActiveCompensationsEnabled The "Working offsets" function is enabled. This function de‐
pends on the machine configuration. Unique D number,
magazine location adapter and magazine management
must be set.
False - default setting, the "Working offsets" function is not
enabled.
M2NLockEnabled Locking of an M to N switchover while a function of the tool
management is being executed.
True - default setting, switchover is locked.
SDToolLengthInListEnabled True - default setting, evaluation of SD42940, SD42942,
and SD42950 in axis name display in the tool lists.
False - the setting data are not evaluated in the axis name
display.
DisableMultiTools True - even though the Multitools function is set in the NC,
they are not offered in the tool lists.
False - default setting, if the Multitools function is set in the
NC, they are offered in the tool lists.
CursorPositionInfoEnabled True - information about the tool on which the cursor is posi‐
tioned is written to the SlCap local variable "/Hmi/TMHMI‐
CurData".
False - default setting, no information about the tool on
which the cursor is positioned is made available on an in‐
terface for the OA.
EnableMonAndBasisGrindingToolTypes True - enable switchover of grinding tool types in respect of
"with/without grinding-specific tool monitoring," "with/with‐
out consideration of the base dimension when calculating
the grinding wheel radius."
False - default setting, switchover not enabled.
ErrorMessageWithoutProgressBar True - error messages are output without a progress bar
and must be acknowledged via softkey.
False - default setting, error message is automatically
closed when the progress bar reaches the end.
ColumnZoomByResolution True - column width is adapted to the resolution of the HMI.
False - default setting, the column width is adapted to the
font size in the HMI. With this setting, with higher resolutions
more columns can be displayed next to each other without
needing to scroll.
AccessLevelReadDetailsAllParameter The following entry specifies the access level as of which
the "Further details" function is offered in the "Details" dialog.
Default setting: Access level 7 (keyswitch position 0) - can
be overlaid through the setting in MD51198.
FixNumberOfMultiToolPlaces Multitools are created with a fixed number of multitool loca‐
tions. There is no prompt when you create the multitool.
Entries Meaning
FixKindOfDistInMultiTools Multitools are created with a fixed type of clearance input of
the multitool locations. There is no prompt when you create
the multitool.
Possible input value: 3 - clearance of the multitool locations
as an angle.
DlDisplayMode ● DisplayDistributed - default setting, the setup offsets EC
are displayed in the tool list and the additive offsets SC
are displayed in the tool wear list.
● EcInWearList - the setup offsets EC are displayed in the
tool wear list and the additive offsets SC are not
displayed.
CombinedToolMonitoring Specifies the combined monitoring types offered in the tog‐
gle field:
● Time/Count - tool life and workpiece count
● Time/Wear - tool life and wear monitoring
● Count/Wear - workpiece count and wear monitoring
● Time/WearDlSc - tool life and wear monitoring for
additive and setup offsets
● Count/WearDlSc - workpiece count and wear monitoring
for additive and setup offsets
● Time/Count/Wear - tool life, workpiece count and wear
monitoring
● Time/Count/WearDlSc - tool life, workpiece count and
wear monitoring for additive and setup offsets
FiltersCombinedWithOr Defines the filter criteria, which are linked in the filter window
using a logical OR. The default setting for all the filter criteria
is a logical AND. The possible entries are:
● "StandBy" - for tools that are ready for use
● "Active" - for tools with active identifier
● "Locked" - for locked tools
● "Prewarn" - for the prewarning limit
● "RemainingPieces" - for the remaining unit quantity
● "RemainingTime" - for the remaining tool time
● "MarkedToUnload" - for the unload identifier
● "MarkedToLoad" - for the load identifier
MagazineMoveMessage True - "Magazine movement running" or "Magazine move‐
ment ended" message is displayed.
False - default setting, message is not displayed.
ToolLoadErrorMessage Refers to the output of the fault message due to a negative
PLC.
True - default setting, the fault message is displayed.
False - the fault message is not displayed.
Entries Meaning
ShowSymbolActivePlace Marking of the magazine location at the machining position.
True - default setting applies for the "Turret" magazine type.
False - setting for all other magazine types.
ShowSymbolActiveMultiToolPlace Marking of the multitool location at the machining position. Is
only displayed when the multitool is located in the spindle or
the tool holder.
True - default setting.
ShowSymbolLoadPlace Selection of the magazine location at the loading position.
True - default setting applies for all magazine types (except
Turret is true).
False - setting for the "Turret" magazine type.
ShowSymbolChangeInSpindlePlace Marking of the magazine location at the change position.
True - default setting applies for all magazine types (except
Revolver is true).
False - setting for the "Turret" magazine type.
ShowSymbolActiveTool Marking of the active tool.
False - default setting.
ShowSymbolProgrammedTool Marking of the follow-on tool.
True - default setting.
ShowSymbolActiveDNo Marking of the active cutting edge.
False - default setting.
ShowSymbolActiveDNoInTool Marking of the active tool by marking the active cutting edge.
True - default setting for configuration without magazine
management.
False - setting for configuration with magazine management.
ShowSymbolAcitveDlNo Marking of the active DL number.
True - default setting.
ShowConflictPositionAndDirection Marking of a conflict; tool position and cutting direction do not
match.
True - default setting.
ShowConflictActiveToolWarning Marking of a conflict; turret magazine type and the active tool
are not at the the machining position.
True - default setting.
Example
<SETTINGS>
<ReactivateWithMagPos value="false" type="bool" />
<MagazineMoveMessage value="false" type="bool" />
<LISTCONFIGURATION> tag
The entries used for configuring the following list views are located in the
<LISTCONFIGURATION> tag:
● "Tool List" window, identifier <SlTmToollistForm>, see the 1st example.
● "Tool Wear" window, <SlTmToolwearForm> identifier
● "Magazine" window, <SlTmToolmagazinForm> identifier
● "Tool Data OEM" window, <SlTmTooloemForm>identifier
This window is hidden in the default configuration. The window is only displayed when you
enable it with <Enabled>, see the 3rd example.
● "Tool Selection" window, <SlTmToolselectionForm> identifier: In order to select a tool
this window can be displayed in the program input screen.
Entry Meaning
Enabled True - window is displayed.
False - window is hidden.
CAPTION Definition of the list name.
Text Used as label/item below the "CAPTION" to define the heading text.
COLUMNX Column selection: X stands for the column number.
TOOLTYPE_ALL The column setting applies to all tool types.
TOOLTYPE_ALL_XXX The column setting applies to all tool types of a group. XXX stands for
the group number of the tool types. The hundreds position is used as the
group number, for example, TOOLTYPE_ALL_100 or TOOL‐
TYPE_ALL_200 etc.
TOOLTYPE_XXX The column setting applies to a particular tool type. XXX stands for the
number of the tool type.
EMPTY_MAG_PLACE The column setting applies to an empty magazine location. Empty mag‐
azine locations appear in a list sorted according to magazine.
Item Identifier of the list parameter.
See example: The column in which the magazine location type is dis‐
played is created with the identifier "MagPlaceType."
Tool parameter identifiers (Page 151)
Cutting edge parameter identifiers (Page 153)
Monitoring parameter identifiers (Page 156)
Magazine location parameter identifiers (Page 158)
Entry Meaning
DELETE_COLUMN Delete column.
INSERT_COLUMN Insert column.
Note
Independent of their programming, the entries are effective in the following sequence:
1. COLUMNX
2. DELETE_COLUMN
3. INSERT_COLUMN
Note
The Enabled entry does not apply for the "Tool Selection" window. The other entries apply.
Example 1: Configuring the magazine list - magazine location and tool location type
Note
The columns of the list configuration cannot be taken from the display in the user interface in
all cases because some columns are automatically inserted and therefore not included in the
count of the configuration.
Variant 1
Column 10 and column 11 are overwritten. If column 10 and column 11 do not exist, the new
columns will be added to the existing columns.
<LISTCONFIGURATION>
<!-- **** Magazine list *** -->
<SlTmToolmagazinForm>
<!-- **** Column 10 *** -->
<COLUMN10>
<!-- **** For all tool types *** -->
<TOOLTYPE_ALL>
<!-- **** Display magazine location type *** -->
<Item value="MagPlaceType" type="QString" />
</TOOLTYPE_ALL>
</COLUMN10>
<!-- **** Column 11 *** -->
<COLUMN11>
<!-- **** For all tool types *** -->
<TOOLTYPE_ALL>
<!-- **** Display tool location type *** -->
<Item value="ToolPlaceSpec" type="QString" />
</TOOLTYPE_ALL>
<!-- **** For all multitools *** -->
<TOOLTYPE_9997>
<!-- **** Display for all multitool location types *** -->
<Item value="MultiToolPlaceSpec" type="QString" />
</TOOLTYPE_9997>
</COLUMN11>
</SlTmToolmagazinForm>
</LISTCONFIGURATION>
Variant 2
The new columns are inserted in the standard configuration between the "Magazine location
locked" and "Oversized tool" columns.
<LISTCONFIGURATION>
<!-- **** Magazine list *** -->
<SlTmToolmagazinForm>
<!-- **** Insert column *** -->
<INSERT_COLUMN>
<!-- **** Column 7 *** -->
<COLUMN7>
<!-- **** For all tool types *** -->
<TOOLTYPE_ALL>
<!-- **** Display magazine location type *** -->
<Item value="MagPlaceType" type="QString" />
</TOOLTYPE_ALL>
</COLUMN7>
<!-- **** Column 8 *** -->
<COLUMN8>
<!-- **** For all tool types *** -->
<TOOLTYPE_ALL>
<!-- **** Display tool location type *** -->
<Item value="ToolPlaceSpec" type="QString" />
</TOOLTYPE_ALL>
<!-- **** For all multitools *** -->
<TOOLTYPE_9997>
<!-- **** Display for all multitool location types *** -->
<Item value="MultiToolPlaceSpec" type="QString" />
</TOOLTYPE_9997>
</COLUMN8>
</INSERT_COLUMN>
</SlTmToolmagazinForm>
</LISTCONFIGURATION>
Note
The columns of the list configuration cannot be taken from the display in the user interface in
all cases because some columns are automatically inserted and therefore not included in the
count of the configuration.
<LISTCONFIGURATION>
<!-- **** Magazine list *** -->
<SlTmToolmagazinForm>
<!-- **** Delete column 7 *** -->
<DELETE_COLUMN>
<COLUMN7 />
</DELETE_COLUMN>
</SlTmToolmagazinForm>
</LISTCONFIGURATION>
Result
● The "OEM Tool Data" window is displayed. It automatically displays the columns shown in
the figure.
● The new "OEM tools" softkey appears and can be operated.
Tool parameters
For the tool parameters, the following identifiers are used in the configuration file:
Note
Tool name "ToolIdent"
The maximum length of tool names is 31 ASCII characters.
The number of characters is reduced for Asian characters or Unicode characters.
The following special characters are not permitted: | # "
EdgeNo D number -
EdgeNoIdx Cutting edge number -
ToolType Tool type, cutting edge parameter 1 $TC_DP1
CuttEdgePos Cutting edge position, cutting edge param‐ $TC_DP2
eter 2
GeoLength1 Length 1, cutting edge parameter 3 $TC_DP3
GeoLengthGeoAx1 Length of geometry axis 1, cutting edge $TC_DP3
parameter 3, e.g. length X
GeoLengthGeoAx1DiscDiameter Grinding wheel diameter in geometry axis $TC_DP3
1, cutting edge parameter 3
GeoLengthGeoAx1DresserDiameter Dressing tool diameter in geometry axis 1, $TC_DP3
cutting edge parameter 3
GeoLength Length, cutting edge parameter 3 $TC_DP3
GeoLength2 Length 2, cutting edge parameter 4 $TC_DP4
The following parameters are assigned to the cutting edges of the grinding tool:
Identifier/parameter Meaning
GrindingMonitoring Grinding-specific tool monitoring
GrindingUseBaseLength Taking into account the base dimension when calculating the
grinding wheel radius
Parameter corresponds to the system variable or the system variable is the basis for this
*)
parameter.
Parameter corresponds to the system variable or the system variable is the basis for this
*)
parameter.
Parameter corresponds to the system variable or the system variable is the basis for this
*)
parameter.
<PARAMETERCONFIGURATION> tag
In the <PARAMETERCONFIGURATION> tag, you have the following options:
1. Changing list parameters.
2. Creating new list parameters based on an existing parameter.
Entries Meaning
HeadLine Column header. Text entered is displayed as a header.
Example: Text "Radius" is displayed as a header (default).
Tooltip Text that is displayed in the tooltip.
Example: Text "Geometry radius" is displayed in the tooltip (default).
ShortText Text if the parameter is displayed in the "More Data" window.
Example: Text "Rad." is displayed in the "More Data" window (default).
DetailsText Text, if the parameter is displayed in the "Details" window.
Example: Text "Radius" is displayed in the "Details" window (default).
Width Column width in pixels in relation to a 640 x 480 resolution.
See example below: The default column width is changed to 53 pixels.
DisplayMode Values that the parameter is displayed with.
See example below: The default setting is changed to "DoubleMode".
The following values can also be accepted:
AnyMode All characters
IntegerMode Integers
UnsignedIntegerMode Unsigned integers
DoubleMode Values with decimal places
The number of decimal places is specified in "Dec‐
imalPlaces"
UnsignedDoubleMode Unsigned values with decimal places
The number of decimal places is specified in "Dec‐
imalPlaces"
Length Specified length
Angle Specified angle
LinearFeedPerTime Linear feed in mm/minute
LinearFeedPerRevolution Linear feed in mm/revolution
LinearFeedPerTooth Linear feed in mm/tooth
RevolutionSpeed Speed
ConstantCuttingSpeed Constant cutting rate
DecimalPlaces Number of decimal places if "DoubleMode" or "UnsignedDoubleMode" is selected
in the DisplayMode.
See example: Two decimal places are entered.
ItemType Field types in which a value is displayed.
TextField Input/output field for values and texts
TextFieldReadOnly Output field for values and texts
CheckBox Input/output field for states
CheckBoxReadOnly Output field for states
BitMask Bit mask for the display of a bit from a value. The bit mask is entered as integer
value. Bit 0 → 1, Bit 1 → 2, Bit 2 → 4
AccessLevel Value for the access level that is used for these parameters in the user interface.
Value range 1 to 7
Entries Meaning
UpperLimit Upper input limit for these parameters in the user interface.
Only applies for numerically entered parameters.
LowerLimit Lower input limit for these parameters in the user interface.
Only applies for numerically entered parameters.
Example
In the following example, the <GeoRadius> parameter is used.
Only enter the modified data.
<PARAMETERCONFIGURATION>
<GeoRadius>
<Width value="53" type="int" />
<DisplayMode value="DoubleMode" type="QString" />
<DecimalPlaces value="2" type="int" />
</GeoRadius>
</PARAMETERCONFIGURATION>
Entries Meaning
Assign new parameter name
See example 1: Text "NewGeoRadius"
Base Name of the parameter on which the new parameter is based.
See example 1: "GeoRadius" parameter is used as a template.
Also enter only the changed data here. All other data is taken from the existing
parameter.
See example 1: Column width changed to 46 pixels. Number of decimal places
changed to 1.
Example 1
<PARAMETERCONFIGURATION>
<NewGeoRadius>
<Base value="GeoRadius" type="QString" />
<Width value="46" type="int" />
<DisplayMode value="DoubleMode" type="QString" />
<DecimalPlaces value="1" type="int" />
</NewGeoRadius>
</PARAMETERCONFIGURATION>
Example 2
Entries Meaning
Assign new cutting edge parameter name
The name is "EdgeUser_1_Bit0" in the following example.
Base Name of the parameter on which the new parameter is based.
In the following example, the "EdgeUser_1" parameter is used as template.
Also enter only the changed data here. All other data is taken from the existing
cutting edge parameter.
The following entries are changed:
Field type: Input/output field for states
Value output: All characters
Bit mask: Bit 0
Column width changed to 17 pixels.
Header changed to "TM_HL_EDGE_USER_1_Bit0"
Text in the tooltip changed to "TM_TT_EDGE_USER_1_Bit0"
<PARAMETERCONFIGURATION>
<EdgeUser_1_Bit0>
<Base value="EdgeUser_1" type="QString" />
<ItemType value="CheckBox" type="QString" />
<DisplayMode value="AnyMode" type="QString" />
<BitMask value="1" type="int" />
<Width value="17" type="int" />
<HeadLine value="TM_HL_EDGE_USER_1_Bit0" type="QString" />
<ToolTip value="TM_TT_EDGE_USER_1_Bit0" type="QString" />
</EdgeUser_1_Bit0>
</PARAMETERCONFIGURATION>
Grinding tool types 401, 402, 403 as well as 411, 412, 413 are not listed as tool types that can
be selected. The grinding-specific tool monitoring - taking into account the basic dimension
when calculating the grinding wheel radius - is set using dedicated parameters. These
parameters act on the tool types in the usual form.
<TOOLTYPECONFIGURATION> tag
The entries used for configuring the tool types are located in the
<TOOLTYPECONFIGURATION> tag:
Entries Meaning
TOOLTYPE_XXX XXX stands for the number of the tool type.
For the assignment of the tool type and number, please refer to Section
"List of tool types (Page 165)".
Tooltype Number (XXX) of the tool type
Name Text identifier of the tool name. The tool name is displayed in the following
windows:
● "New Tool - Favorites"
● "New Tool - Milling Cutter 100 - 199"
● "New Tool - Drill 200 - 299"
● "New Tool - Grinding Tool 400 - 499"
● "New Tool - Special and Auxiliary Tools 700 - 900"
See example: For the text identifier "TM_PAR_SHANK_END_CUTTER",
the name "End mill" appears on the user interface.
Shortname Text identifier of the tool name. Tool name is displayed in the tool list.
See example: For the text identifier "TM_PPTT_SHANK_END_CUTTER",
the name "MILLING CUTTER" appears on the user interface.
Tooltip Text identifier of the tool name. This tool name is displayed in the tooltip.
See example: For the text identifier "TM_TTTT_SHANK_END_CUTTER",
the name "End mill" appears on the user interface.
Entries Meaning
Icon9 - for milling technology Icon representing the tool type.
The icons are displayed in the following windows:
● "Tool List" in the "Type" column
● "New Tool - Favorites" in the "Tool position" column
● "New Tool - Milling Cutter 100 - 199" in the "Tool position" column
● "New Tool - Drill 200 - 299" in the "Tool position" column
● "New Tool - Special Tool 700 - 900 in the "Tool position" column.
The icons are in ".png" format. They are stored according to image res‐
olution in the following directories:
/oem/sinumerik/hmi/ico/ico640, oder ico800, or ico1024
/user/sinumerik/hmi/ico/ico640, oder ico800, or ico1024
IconX - for the turning and Icon representing the tool type (see Icon9 - for milling technology)
grinding technologies Special feature - tool positions are supported in the turning and grinding
technologies.
X is for the tool position represented by the icon. Position 9 is an unde‐
fined position represented by a cross.
Icon9_2 Icon representing the tool type in cutting edge position 9. It is used when
cutting edge position 9 is to be treated as a valid cutting edge position.
(see <SETTINGS> - CreateNewToolWithCuttPos9Enabled, Chapter
"General settings (Page 142)")
Iconorder Order in which the tool positions, represented by icons, are switched.
DisableInNewToolDialog With this entry, the tool type in question is not offered when new tools
are created. If the tool list finds a tool of this type that already exists, it is
correspondingly displayed.
DELETE_TOOLTYPE All predefined tool types that are not to be supported in the tool lists.
GrindingTooltypes All tool types that are to be used as grinding tool types.
Example 1
<TOOLTYPECONFIGURATION>
<TOOLTYPE_120>
<Tooltype value="120" type="uint" />
<Name value="TM_PAR_SHANK_END_CUTTER" type="QString" />
<Shortname value="TM_PPTT_SHANK_END_CUTTER" type="QString" />
<Tooltip value="TM_TTTT_SHANK_END_CUTTER" type="QString" />
<Icon9 value="to_poly_shank_end_cutter_down.png" type="QString" />
</TOOLTYPE_120>
</TOOLTYPECONFIGURATION>
Example 2
<TOOLTYPECONFIGURATION>
<DELETE_TOOLTYPE>
<TOOLTYPE_110 />
</DELETE_TOOLTYPE>
</TOOLTYPECONFIGURATION>
<MOREDATACONFIGURATION> tag
The entries used for configuring the "Additional Data" window are located in the
<MOREDATACONFIGURATION> tag. Various data items can be displayed for each tool type
in a number of rows and columns. Each data item to be displayed is specified by entering a
list parameter:
Tool parameter identifiers (Page 151)
Cutting edge parameter identifiers (Page 153)
Monitoring parameter identifiers (Page 156)
A brief description of the parameter (ShortText) then appears in the window with the value
itself beside it. Configuring list parameters (Page 161).
If another description text is required in the "More Data" window, a text can also be entered in
a row or column. In the window, the width of the text is made to conform to that of the brief
description and value of a parameter.
Any number of rows and columns can be created. A scrollbar appears when the window
reaches a certain size.
Entries Meaning
TOOLTYPE_XXX Number of the tool type.
See example: Tool type 111 = Ball end mill (tapered die-sinking cutter).
ROWX_COLY Particular rowX_columnY.
If there is no entry after rowX and columnY, this field remains blank.
See example: In the "More Data" window, the first row is blank.
Item The following entries are possible:
● Parameter identifier
● Text
See example:
The header "Corner radius" appears in the second row of the window.
The text "Radius" and an input field for the value appear in the third row of
the window.
The fourth row is blank.
TOOLTYPE_ALL_XXX The setting applies to all tool types of a group. XXX stands for the group
number of the tool types. The hundreds position is used as the group num‐
ber, for example, TOOLTYPE_ALL_100 or TOOLTYPE_ALL_200 etc. (see
example).
WITHOUT_MORE_DA‐ Tool types of a tool group for which no "further data" are to be displayed can
TA be excluded with this identifier (see example).
Example 1
<MOREDATACONFIGURATION>
<TOOLTYPE_111>
<ROW1_COL1>
</ROW1_COL1>
<ROW2_COL1>
<Item value="TM_DGL_CORNER_RADIUS" type="QString" />
</ROW2_COL1>
<ROW3_COL1>
<Item value="GeoCornerRadius" type="QString" />
</ROW3_COL1>
<ROW4_COL2>
</ROW4_COL2>
</TOOLTYPE_111>
</MOREDATACONFIGURATION>
Example 2
<MOREDATACONFIGURATION>
<TOOLTYPE_ALL_500>
<ROW1_COL1>
<Item value="TM_DGL_LENGTH" type="QString" />
</ROW1_COL1>
<ROW2_COL1>
<Item value="GeoLengthGeoAx3" type="QString" />
</ROW2_COL1>
...
</TOOLTYPE_ALL_500>
<WITHOUT_MORE_DATA>
<TOOLTYPE_580 />
</WITHOUT_MORE_DATA>
</MOREDATACONFIGURATION>
<NEWTOOLFAVORITECONFIGURATION> tag
In the tag <NEWTOOLFAVORITECONFIGURATION> you define the tool types that are most
frequently used. The specified tool types are displayed in the "New Tool - Favorites" window.
Entries Meaning
StaticTooltypes Numbers of tool types Enter the individual numbers, separated by blanks.
The following section describes the assignment of the tool type and num‐
ber: List of tool types (Page 165)
Example
<NEWTOOLFAVORITECONFIGURATION>
<StaticTooltypes value="120 140 200 220 710 711" type="QString"/>
</NEWTOOLFAVORITECONFIGURATION>
<NEWTOOLCONFIGURATION> tag
You use the "New Tool" dialog to supply a new tool with specific tool data before creating the
tool or before loading the tool to a magazine location. These are typically the tool size and/or
the tool location type because these parameters can no longer be changed when the tool is
loaded. It is also useful to display the tool type and the tool names in this window.
Specify the parameters in the <NEWTOOLCONFIGURATION> tag that are to be displayed in
the "New Tool" dialog.
Note
The number of parameters is limited by the size of the window.
Entries Meaning
ItemX Entry of the identifier of the tool parameter. "X" specifies the order in which the pa‐
rameters are displayed in the window.
The identifier of the tool parameter can be found in Chapter:
Tool parameter identifiers (Page 151)
Example
<NEWTOOLCONFIGURATION>
<!-- The standard field "oversized tool" is removed and replaced by the fields -->
<!-- "tool location type", "tool size left" and "tool size right" -->
<!-- -->
<Item2 value="ToolPlaceSpec" type="QString"/>
<Item3 value="ToolSizeLeft" type="QString"/>
<Item4 value="ToolSizeRight" type="QString"/>
</NEWTOOLCONFIGURATION>
<NEWMULTITOOLCONFIGURATION> tag
You use the "New Multitool" dialog to supply a new multitool with specific multitool data before
creating the multitool or loading it into to a magazine location. Multitool data typically includes
the number of multitool locations and spacing between locations, as these parameters cannot
be changed once the multitool has been created. The same applies to the multitool size and/
or multitool location type as to the tool size and tool location type. These parameters, too,
cannot be changed once they have been loaded into the tool. It is also a good idea to display
the multitool name in this window.
Entries Meaning
ItemX Entry of the identifier of the multitool parameter. "X" specifies the order in
which the parameters will be displayed in the window.
The identifier of the multitool parameter can be found in Chapter:Multitool
parameter identifiers (Page 159)
<NEWTOOLIDENTCONNECTIONCONFIGURATION> tag
You use the "New Tool from Code Carrier" dialog to identify a new tool before creating it. It is
therefore a good idea to display the tool type and the tool name in this window. In addition, the
same rules apply as for configuration of the window "New Tool," Section "Configuring the "New
Tool" window (Page 172)."
In the <NEWTOOLIDENTCONNECTIONCONFIGURATION>tag, define the parameters that
you wish to have displayed in the "New Tool of Code Carrier" dialog.
Entries Meaning
ItemX Entry of the identifier of the tool parameter. "X" specifies the order in which the pa‐
rameters are displayed in the window.
The identifier of the tool parameter can be found in Chapter:
Tool parameter identifiers (Page 151)
<NEWTOOLSAVETOOLDATACONFIGURATION> tag
You use the "New Tool from File" dialog to identify a new tool before creating it. It is therefore
a good idea to display the tool type and the tool name in this window. In addition, the same
rules apply as for configuration of the window "New Tool," Section "Configuring the "New Tool"
window (Page 172)."
Specify the parameters in the <NEWTOOLSAVETOOLDATACONFIGURATION>tag that are
to be displayed in the "New Tool from Tile" dialog.
Entries Meaning
ItemX Entry of the identifier of the tool parameter. "X" specifies the order in which the pa‐
rameters are displayed in the window.
The identifier of the tool parameter can be found in Chapter:
Tool parameter identifiers (Page 151)
<NEWTOOLDEFAULTVALUECONFIGURATION> tag
In the <NEWTOOLDEFAULTVALUECONFIGURATION> tag, you can specify default values
for tools that you create via the user interface. These values can be configured depending on
the tool type and, if required, also depending on the cutting edge position:
Entries Meaning
TOOLTYPE_ALL The parameter setting applies to all tool types.
TOOLTYPE_XXX The parameter setting applies to a specific tool type. XXX stands for the
number of the tool type.
CUTTEDGEPOS_XXX The parameter setting applies to a specific cutting edge position. XXX
stands for the number of the cutting edge position.
Default Default value of the parameter.
Example
<NEWTOOLDEFAULTVALUECONFIGURATION>
<!-- Initialize geometry length 1 for all tool types to 70.0 -->
<TOOLTYPE_ALL>
<GeoLengthGeoAx1>
<Default value="70.0" type="double" />
</GeoLengthGeoAx1>
</TOOLTYPE_ALL>
<!-- Initialize tip angle of the twist drill to 120.0 -->
<TOOLTYPE_200>
<NoseAngle>
<Default value="120.0" type="double" />
</NoseAngle>
</TOOLTYPE_200>
<TOOLTYPE_500>
<!-- Initialize plate angle of the roughing tool to 82.0 -->
<PlateAngle>
<Default value="82.0" type="double" />
</PlateAngle>
<!-- Initialize holder angle of the roughing tool depending on the cutting edge position
-->
<HolderAngle>
<CUTTEDGEPOS_1>
<Default value="93.0" type="double" />
</CUTTEDGEPOS_1>
<CUTTEDGEPOS_2>
<Default value="93.0" type="double" />
</CUTTEDGEPOS_2>
<CUTTEDGEPOS_3>
<Default value="93.0" type="double" />
</CUTTEDGEPOS_3>
<CUTTEDGEPOS_4>
<Default value="93.0" type="double" />
</CUTTEDGEPOS_4>
<CUTTEDGEPOS_5>
<Default value="49.0" type="double" />
</CUTTEDGEPOS_5>
<CUTTEDGEPOS_6>
<Default value="49.0" type="double" />
</CUTTEDGEPOS_6>
<CUTTEDGEPOS_7>
<Default value="49.0" type="double" />
</CUTTEDGEPOS_7>
<CUTTEDGEPOS_8>
<Default value="49.0" type="double" />
</CUTTEDGEPOS_8>
</HolderAngle>
</TOOLTYPE_500>
<!-- Initialize coolant 2 of the plunge cutter to switched on -->
<TOOLTYPE_520>
<Coolant2>
<Default value="true" type="bool" />
</Coolant2>
</TOOLTYPE_520>
</NEWTOOLDEFAULTVALUECONFIGURATION>
The following combinations between the cutting-edge position and the cutting direction result
dependent on the tool type. When creating the new tool, the operator selects a combination
in the "New Tool - Favorites" window.
The plate angle rather than the clearance angle is displayed on the screen:
plate angle = 180 - holder angle - clearance angle
Tool type $TC_DP1 Unit of measure‐ Default value $TC_DP8 for plate length
ment
Type 500 roughing tool metric 11
Type 510 finishing tool inch 0.4
For all grinding tools, the parameter for calculating the radius:
$TC_TPG9 = 3 (corresponds to length 1) applies
<DETAILSCONFIGURATION> tag
In the tag <DETAILSCONFIGURATION>, you can make the settings for the "Detail" window:
Entries Meaning
ShowToolNumber The tool number is displayed in the upper right field of the "Detail" window.
UseAxisNameInLength The tool length is displayed with axis identifiers, for example, Length X
instead of Length 1.
If no data is specified, then the setting is taken from the tool lists.
ShowBaseLength The basic length is displayed in the "Detail" window (AdaptLength1,
AdaptLength2 and AdaptLength3).
If no data is specified, then the setting is taken from the tool lists.
ShowYAxis The Y axis is displayed in the "Detail" window.
If no data is specified, then the setting is taken from the tool lists.
AutoDisplayAxisEnabled Several components of the tool length are displayed, even if only one
tool length is displayed in the tool list.
Example
<DETAILSCONFIGURATION>
<ShowToolNumber value="true" type="bool" />
</DETAILSCONFIGURATION>
<MAGAZINEPLACENAMECONFIGURATION> tag
The entries to assign dedicated magazine location names are located in the
<MAGAZINEPLACENAMECONFIGURATION> tag. Magazine locations can be displayed with
texts. Instead of the identifier, e.g. 1/5 for the first magazine, location five, the configured text
is then output in the tool lists.
Entries Meaning
MAGAZINE_XXX XXX stands for the magazine number.
PLACE_XXX XXX stands for the location number.
Name Text identifier of the magazine location.
Example
<MAGAZINEPLACENAMECONFIGURATION>
<MAGAZINE_9998>
<PLACE_2>
<Name value="TM_SPECIAL_MAG_PLACE_1" type="QString" />
</PLACE_2>
</MAGAZINE_9998>
<MAGAZINE_1>
<PLACE_3>
<Name value="TM_SPECIAL_MAG_PLACE_2" type="QString" />
</PLACE_3>
</MAGAZINE_1>
</MAGAZINEPLACENAMECONFIGURATION>
Example
Magazine 1 should have the name "main magazine".
$TC_MAP2[1]="main magazine"
If the "main magazine" text is to be output language-dependent, then the language-dependent
texts for the text identifier "main magazine" must be created.
See also
Please refer to the following section for the procedure to create language-dependent text:
Creating OEM texts (Page 198)
<MULTITOOLPLACETOOLTIPCONFIGURATION> tag
You will find the entries for assigning tooltips in the tag
<MULTITOOLPLACETOOLTIPCONFIGURATION>. This is particularly useful if all the
multitools used on a turning machine have two locations and a fixed assignment between
multitool locations and the main spindle or the counter spindle exists, for example,
location 1 - main spindle location 2 - counter spindle. In this case, the tooltip for location 1
could be "Tool Holder for Main Spindle."
Entries Meaning
PLACE_XXX XXX stands for the multitool location number.
Tooltip Text identifier of the magazine location.
Example
<MULTITOOLPLACETOOLTIPCONFIGURATION>
<PLACE_1>
<ToolTip value="TM_HOLDER_OF_MAIN_SPINDLE" type="QString" />
</PLACE_1>
<PLACE_2>
<ToolTip value="TM_HOLDER_OF_COUNTER_SPINDLE" type="QString" />
</PLACE_2>
</MULTITOOLPLACETOOLTIPCONFIGURATION>
See also
Please refer to the following section for the procedure to create language-dependent text:
Creating OEM texts (Page 198)
<PLACETYPECONFIGURATION> tag
You can find entries to allocate your own location type identifiers in the tag
<PLACETYPECONFIGURATION>. Magazines and magazine location types can be displayed
with texts in the tool lists. Instead of identifier 2, e.g. for location type 2, the configured text is
then output in the tool lists.
Entries Meaning
PLACETYPEXXX XXX stands for the number of the location type.
Text Text identifier of the location type.
Tooltip Tooltip text identifier of the location type.
Example
<PLACETYPECONFIGURATION>
<PLACETYPE1>
<Text value="TM_PLACETYPE_1" type="QString" />
<Tooltip value="TM_TT_PLACETYPE_1" type="QString" />
</PLACETYPE1>
<PLACETYPE2>
<Text value="TM_PLACETYPE_2" type="QString" />
<Tooltip value="TM_TT_PLACETYPE_2" type="QString" />
</PLACETYPE2>
<PLACETYPE3>
<Text value="TM_PLACETYPE_3" type="QString" />
<Tooltip value="TM_TT_PLACETYPE_3" type="QString" />
</PLACETYPE3>
</PLACETYPECONFIGURATION>
See also
Please refer to the following section for the procedure to create language-dependent text:
Creating OEM texts (Page 198)
Requirement
Turning technology or milling technology and technology extension turning have been set:
Name of the associated configuration file sltmturninglistconfig.xml or sltmmillturnlistconfig.xml.
location which is assigned a channel via this configuration, then the tool icon is output
depending on this position that has been set.
This setting option is only available in turning technology and in milling technology with the
technology extension milling. This can be especially helpful if, on a multi-channel machine, a
magazine is used before the turning center and another magazine after the turning center.
This means that the tools can be entered into the tool list in a position visible for the operator.
The assignment between magazine locations and channels is useful when instead of two
magazines, two tool holders/tool spindles exist that fetch their tools from a magazine. One tool
holder is used in front of the turning center and one is used behind the turning center, so that
different views onto the tool result.
<CHANNELMAGAZINEASSIGNMENT> tag
In tag <CHANNELMAGAZINEASSIGNMENT> , you will find the entries for the assignment
between the magazines or magazine locations and the channels.
Entries Meaning
CHANNELNO_XXX XXX stands for the channel number.
Magazines Number of magazines that are assigned to the channel.
MAGAZINE_XXX Number of the magazine whose locations will be assigned to the channel.
Places Number of magazine locations that will be assigned to the channel.
Example 1
The following assignment between magazine and channel should apply:
<CHANNELMAGAZINEASSIGNMENT>
<CHANNELNO_1>
<Magazines value="1 2 3" type="QString" />
</CHANNELNO_1>
<CHANNELNO_2>
<Magazines value="4" type="QString" />
</CHANNELNO_2>
<CHANNELNO_3>
<Magazines value="5" type="QString" />
</CHANNELNO_3>
<CHANNELNO_4>
<Magazines value="6" type="QString" />
</CHANNELNO_4>
</CHANNELMAGAZINEASSIGNMENT>
Example 2
Magazine location 1 of the buffer will be assigned to channel 1.
Magazine location 2 of the buffer will be assigned to channel 2.
<CHANNELMAGAZINEASSIGNMENT>
<CHANNELNO_1>
<MAGAZINE_9998>
<Places value="1" type="QString" />
</MAGAZINE_9998>
</CHANNELNO_1>
<CHANNELNO_2>
<MAGAZINE_9998>
<Places value="2" type="QString" />
</MAGAZINE_9998>
</CHANNELNO_2>
</CHANNELMAGAZINEASSIGNMENT>
12.2.18 Assignment between magazines and magazine locations and coordinate systems
Requirement
Turning technology or milling technology and technology extension turning have been set:
Name of the associated configuration file sltmturninglistconfig.xml or sltmmillturnlistconfig.xml.
Assignment between the magazine or magazine locations and the coordinate system
With this setting, magazines and magazine locations can be assigned to coordinate systems.
This is useful if the machine is configured in such a way that a magazine or magazine location
does not match the position of the coordinate system set in the channel. The assignment
between magazine or magazine location and coordinate system can be defined here.
As a consequence of this configuration, the tool icons are output with reference to their position
depending on the coordinate system.
This setting option is only available in turning technology and in milling technology with the
technology extension milling.
<COORDSYSMAGAZINEASSIGNMENT> tag
In tag <COORDSYSMAGAZINEASSIGNMENT>, you will find the entries for the assignment
between magazines or magazine locations and coordinate systems.
Entries Meaning
COORDSYSNO_XXX XXX stands for the number of the coordinate system.
Magazines Number of the magazines that are assigned to the channel.
Entries Meaning
MAGAZINE_XXX Number of the magazine whose locations will be assigned to the coordinate
system.
Places Number of magazine locations that will be assigned to the coordinate system.
Example
The following assignment between magazines or magazine locations and coordinate systems
is to apply:
<COORDSYSMAGAZINEASSIGNMENT>
<COORDSYSNO_34>
<Magazines value="1 3 4" type="QString" />
</COORDSYSNO_34>
<COORDSYSNO_33>
<Magazines value="2" type="QString" />
<MAGAZINE_9998>
<Places value="2" type="QString" />
</MAGAZINE_9998>
</COORDSYSNO_33>
</COORDSYSMAGAZINEASSIGNMENT>
Entries Meaning
NewTool New tool
Edges Cutting edges
Entries Meaning
FirstEdge Filter "Only first cutting edge," default setting "Edges"
StandBy Filter "Only tools that are ready to use," default setting "NewTool"
Active Filter "Only tools with active code," default setting "NewTool"
Locked Filter "Only disabled tools," default setting "NewTool"
Prewarning Filter "Only tools that have reached the pre-alarm limit," default setting "New‐
Tool"
RemainingPieces Filter "Only tools with remaining quantity," default setting "NewTool Edges"
MarkedToUnload Filter "Only tools with unload identifier," default setting "NewTool Edges"
MarkedToLoad Filter "Only tools with load identifier," default setting "NewTool Edges"
Example
<FILTERCONFIGURATION>
<SOFTKEYLOCK>
<Locked value="NewTool Edges" type="QString" />
</SOFTKEYLOCK>
</FILTERCONFIGURATION>
<LOADSTATIONSHANDLEALLTOOLS> tag
For functions "Delete all," "Unload all," and "Load all," you must specify a load station if multiple
load stations are configured in the magazine configuration of the NC. The load station is defined
in a dialog called "Select Load Station" or via the load station configuration with tag
<LOADSTATIONSHANDLEALLTOOLS>.
Entries Meaning
DialogEnabled Offer window "Load Station Selection," default setting "true"
MAGAZINE_XXX Number of the magazine to which a load station will be assigned.
LoadStation Load station to be assigned to the magazine.
Example
<LOADSTATIONSHANDLEALLTOOLS>
<DialogEnabled value="true" type="bool" />
<MAGAZINE_1>
<LoadStation value="2" type="uint" />
</MAGAZINE_1>
<MAGAZINE_2>
<LoadStation value="1" type="uint" />
</MAGAZINE_2>
</LOADSTATIONSHANDLEALLTOOLS>
The M functions for the tool-specific functions are executed by the ShopMill cycles at the tool
change. If the checkbox is activated, the corresponding M code is generated from MD52281.
If the checkbox is not activated, the corresponding M code is generated from MD52282.
If you do not want to automatically execute additional M commands at the tool change, then
set the associated machine data to -1 for the M commands of this tool-specific function. This
also hides the associated fields in the tool list.
The default value of the machine data is -1 so that no M values are output for the corresponding
functions.
Technical procedure
The M functions for the tool-specific functions are generated by the ShopMill cycles in a set
(up to four M commands are possible).
The number and also the sequence of the M commands are dependent on the settings of the
machine data (MD52281 to MD52282) and the programming.
If M functions less than 100 are used, the number and sequence of the M commands has no
significance. They are located in the user PLC in the decoded area (DB21.DBB194 to
DB21.DBB206), independent of the number and the sequence when programming.
However, if M functions from 100 and higher are used, then you must decode these yourself
in the user PLC. In this case, you must take into consideration the number and sequence (M
function 1 to M function 4).
JOG mode
In the JOG mode, no coolant and tool-specific functions are output to the interface. For a tool
change in the JOG mode, these functions can be initiated by the operator using the keys on
the machine control panel (implementation via the PLC user program).
MD52281 $MCS_TOOL_MCODE_FUNC_ON[0] = 90
MD52281 $MCS_TOOL_MCODE_FUNC_ON[1] = 92
MD52281 $MCS_TOOL_MCODE_FUNC_ON[2] = 94
MD52281 $MCS_TOOL_MCODE_FUNC_ON[3] = 96
MD52282 $MCS_TOOL_MCODE_FUNC_OFF[0] = 91
MD52282 $MCS_TOOL_MCODE_FUNC_OFF[1] =-1
MD52282 $MCS_TOOL_MCODE_FUNC_OFF[2] = 95
MD52282 $MCS_TOOL_MCODE_FUNC_OFF[3] = 97
As a result, fields 1 to 4 of the tool-specific functions are displayed in the tool list.
The following fields are activated:
Tool-specific function 1: On
Tool-specific function 2: Off
Tool-specific function 3: Off
Tool-specific function 4: Off
The M functions M90, M95 and M97 are generated by the ShopMill cycles at the tool change.
You can change the texts for "Coolant 1/2 on/off" and "Tool-spec. fct. 1, ..." (see Section
Identifiers of the standard texts (Page 199)). So that the texts between the tool list and program
area machine functions match, please note the following section.
If you require the texts in additional languages, then you must create a separate file for each
language. The names of the files only differ by the language code "xxx" (Supported
languages (Page 612)). Use only the specified language codes.
Tag Meaning
source Text identifier for label: SlStepLabels
A maximum of up to four M functions can be defined:
T_LAB_USER_MACHINE_FUNC_1
T_LAB_USER_MACHINE_FUNC_2
T_LAB_USER_MACHINE_FUNC_3
T_LAB_USER_MACHINE_FUNC_4
Text identifier for tooltip: SlStepToolTip
There are 3 tooltips for every machine function x (1 - 4):
T_TT_USER_MACHINE_FUNC_x: Standard tooltip if the machine function was not
selected.
T_TT_USER_MACHINE_FUNC_x _ON: Tooltip when the machine function is acti‐
vated
T_TT_USER_MACHINE_FUNC_x_OFF: Tooltip for deactivated machine function
translation Text, which is displayed at the user interface.
Label texts: You can only enter texts on one line. The "lines" entry is not applicable.
Tooltip: You can enter multi-line texts. A line break is set using the "%n" character.
chars Text length
The maximum text length is 30 characters.
lines Number of lines
The maximum number of lines is three.
remark Own comment - entry is not displayed at the user interface.
Procedure
1. You can copy the sample file "oem_slstepforms_deu.ts" from the following directory: /
siemens/sinumerik/hmi/template/lng
2. Save or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory.
3. Change the file name to "slstepforms_deu.ts".
If you require texts for additional languages, then a separate file must be created for each
language. Save the file with the appropriate language code in the file name.
4. Open the file and define the texts in the <message> and </message> areas.
5. Restart the system.
The file must still be converted into a binary format in order that the texts are displayed
during the program runtime. This data is only converted during power up.
Precondition
Software option
You require the "MC Information System TDI Statistic" option for this function
Function
When reactivating a tool, you have the option of specifying the reason for the tool change, e.g.
to use this information for statistical purposes. The "Reason for Tool Change" selection window
is opened after pressing the "Reactivate" softkey. In a checkbox, you can select the reason
for the tool change. The tool change is entered in a tool parameter to be configured or in a
local variable of the SlCap service.
<TOOLCHANGEREASON> tag
You configure the function in the <TOOLCHANGEREASON> tag:
Parameter Designation
Enabled True - "Reason for tool change" selection window is displayed when
reactivating.
False - default value, selection window is not displayed.
OnlyOneReasonAllowed It is only permissible to select one tool change reason.
UseCapLocalParameter The reason for the tool change is entered into a local variable of the
SlCap service.
REASONXXX XXX stands for an internal number. The numbers for the tool change
reason must be clear and unique.
Text Text identifier of the tool change reason.
Parameter Parameter identifier of the parameter in which it is entered whether the
tool change reason was selected.
BitMask Bit mask to enter the reason for the change in the local variable of the
SlCap service. The bit mask is entered as integer value. Bit 0 → 1,
bit 1 → 2, bit 2 → 4
Argument Meaning
datetime Date and time of the event
containerNo Number of the management area
toaNo Number of the TO area
toolNo Tool number
edgeNo Cutting edge number
toolIdent Tool name
Argument Meaning
toolDuplo Replacement tool number
ncuName Name of the NCU
reactivationReason Reason for tool change
monitoringMode Monitoring type
remainingBefore Remaining unit quantity/tool lifetime before reactivation
Example 1
The following example uses the texts for the tool change reason, already prepared in the
operating software. In this example, the tool change reason is stored in parameters that still
have to be configured, e.g. the OEM tool data 1, bit 1 and following.
<TOOLCHANGEREASON>
<Enabled value="true" type="bool" />
<REASON1>
<Text value="TM_DGL_DESIRED_PIECES_ELAPSED" type="QString" />
<Parameter value="ToolUser_1_Bit1" type="QString" />
</REASON1>
<REASON2>
<Text value="TM_DGL_TOOL_BREAKAGE" type="QString" />
<Parameter value="ToolUser_1_Bit2" type="QString" />
</REASON2>
<REASON3>
<Text value="TM_DGL_CUTTING_EDGE_DAMAGE" type="QString" />
<Parameter value="ToolUser_1_Bit3" type="QString" />
</REASON3>
<REASON4>
<Text value="TM_DGL_PREMATURE_WEAR" type="QString" />
<Parameter value="ToolUser_1_Bit4" type="QString" />
</REASON4>
<REASON5>
<Text value="TM_DGL_TYPE_REEQUIPPING" type="QString" />
<Parameter value="ToolUser_1_Bit5" type="QString" />
</REASON5>
<REASON6>
<Text value="TM_DGL_TOOL_TRIAL" type="QString" />
<Parameter value="ToolUser_1_Bit6" type="QString" />
</REASON6>
<REASON7>
<Text value="TM_DGL_PREVENTIVE_CHANGE" type="QString" />
<Parameter value="ToolUser_1_Bit7" type="QString" />
</REASON7>
</TOOLCHANGEREASON>
Example 2
Also in this example, the prepared texts for the reason for the change are used. It is only
permitted to enter one reason for the change as a valid entry. The reason for the tool change
is saved in the local variable of the SlCap service.
<TOOLCHANGEREASON>
<Enabled value="true" type="bool" />
<OnlyOneReasonAllowed value="true" type="bool" />
<UseCapLocalParameter value="true" type="bool" />
<REASON1>
<Text value="TM_DGL_DESIRED_PIECES_ELAPSED" type="QString" />
<BitMask value="1" type="int" />
</REASON1>
<REASON2>
<Text value="TM_DGL_TOOL_BREAKAGE" type="QString" />
<BitMask value="2" type="int" />
</REASON2>
<REASON3>
<Text value="TM_DGL_CUTTING_EDGE_DAMAGE" type="QString" />
<BitMask value="4" type="int" />
</REASON3>
<REASON4>
<Text value="TM_DGL_PREMATURE_WEAR" type="QString" />
<BitMask value="8" type="int" />
</REASON4>
<REASON5>
<Text value="TM_DGL_TYPE_REEQUIPPING" type="QString" />
<BitMask value="16" type="int" />
</REASON5>
<REASON6>
<Text value="TM_DGL_TOOL_TRIAL" type="QString" />
<BitMask value="32" type="int" />
</REASON6>
<REASON7>
<Text value="TM_DGL_PREVENTIVE_CHANGE" type="QString" />
<BitMask value="64" type="int" />
</REASON7>
</TOOLCHANGEREASON>
See also
For configuring new parameters, see Configuring list parameters (Page 161).
Requirement
Software option
You require the "Access MyTool ID" option for this function (Tool Ident Connec‐
tion).
<IDENTCONNECTIONCONFIGURATION> tag
The entries used for configuring the code carrier connection in the tool list of the user interface
are located in the <IDENTCONNECTIONCONFIGURATION> tag. The code carrier
connection is implemented via TDI Ident Connection.
The data of the tool are read from the code carrier tool and displayed in the "New Tool"
window. Click OK to create the tool in the NC and to initialize it with the code carrier data.
2. Unloading tools on the code carrier:
The tool is unloaded and the data of the tool is written to the code carrier. The tool can also
be deleted using a setting (see below).
3. Deleting the tool on the code carrier:
The tool is unloaded and the data of the tool is written to the code carrier. The tool is then
deleted from the NC. Using a setting (see below), the "On code carrier" softkey can also
be hidden for deleting a tool.
The following settings can be made:
Entries Meaning
Enabled true - code carrier connection is offered.
false - code carrier connection is not offered.
ShowInternalMessage true - internal messages for error analysis are also displayed.
false - default setting, no internal messages are displayed.
UnloadWithoutIdentconnection true - The "On code carrier" function is not offered during unload‐
ing. It is displayed during "Delete tool."
false - Default setting, the "On code carrier" function is offered
during unloading.
Entries Meaning
UnloadWithDelete true - the tool is deleted when unloaded to the code carrier. The
"On code carrier" function is not offered for "Delete tool".
false - default setting, the tool is only unloaded for "unload to code
carrier" and remains in the NC memory.
OnlyInLoadStation true - default setting, on the one hand, only loaded tools are stored
"on code carrier", on the other hand, new tools "from code carrier"
can be created only directly in the magazine.
false - tools can be created independently of the "from code car‐
rier" magazine slot or deleted "on code carrier".
CreateNewToolWithDialog true - default setting, before creating the tool for code carrier, the
tool data is displayed in the "New Tool" window.
false - the tool is created directly in the tool list.
ForceSisterToolNumber true - The sister tool number specified by the code carrier data is
kept when the tool is created.
false - Default setting, the sister tool number is freely assigned.
UseDefaultData true - The new tool is initialized with the configured default data
before the code carrier data are applied (see tag <NEWTOOL‐
DEFAULTVALUECONFIGURATION> Section "Configuring de‐
fault values for new tools (Page 174)").
false - Default setting, the new tool is not initialized with the con‐
figured default data.
OrderFirstWriteThanUnload true - During unloading/deletion, first the data are written to the
code carrier and then the tool is unloaded or deleted.
false - Default setting, during unloading/deletion first the tool is
unloaded, then the data are written to the code carrier and finally,
if requested, the tool is deleted.
Example
<IDENTCONNECTIONCONFIGURATION>
<Enabled value="true" type="bool" />
<ShowInternalMessage value="false" type="bool" />
<UnloadWithDelete value="false" type="bool" />
<OnlyInLoadStation value="true" type="bool" />
<CreateNewToolWithDialog value="true" type="bool" />
</IDENTCONNECTIONCONFIGURATION>
References
For further information about tool management, please refer to:
Function Manual, SINUMERIK Integrate Access MyTool Ident Connection
(MCIS TDI Ident Connection)
<SAVETOOLDATACONFIGURATION> tag
The entries used for configuring the functions "Save tools to file" or "Create tools from file" are
located in the <SAVETOOLDATACONFIGURATION> tag:
The following functions in the tool list are available:
1. Creating tools from file:
The data of the tool are read from a file and displayed in the "New Tool" window. Click OK
to create the tool in the NC and to initialize it with the data from the file.
2. Unloading tools into a file:
The tool is unloaded and the data of the tool are written to a file. The tool can also be deleted
using a setting (see below).
3. Deleting the tool in a file:
The tool is unloaded and the data of the tool are written to a file. The tool is then deleted
from the NC. The softkey "In File" can be hidden while the tool is deleted by means of a
setting (see below).
Entries Meaning
Enabled true - Tool from/in file is offered.
false - Tool from/in file is not offered.
UnloadWithDelete true - The tool is deleted when unloaded to a file. The "In File" function
is not offered for "Delete tool."
false - Default setting, on Unload to file the tool is only unloaded and is
kept in the NC memory.
CreateNewToolWithDialog true - Default setting, before the tool is created from a file, the tool data
is displayed in the "New Tool" window.
false - The tool is created directly in the tool list.
ForceSisterToolNumber true - The sister tool number specified by the code carrier data is kept
when the tool is created.
false - Default setting, the sister tool number is freely assigned.
UseDefaultData true - The new tool is initialized with the configured default data before
the data are taken over from the file (see tag <NEWTOOLDEFAULTVA‐
LUECONFIGURATION> Section "Configuring default values for new
tools (Page 174)").
false - Default setting, the new tool is not initialized with the configured
default data.
Overview
This section describes how you create OEM texts in a particular language.
The texts are created in the "sltmlistdialog_xxx.ts" file.
A dedicated file must be created for each language. The file names differ by the language code
(Supported languages (Page 612)). For "xxx", set the appropriate language code.
Creating texts
All OEM texts from the previous sections, such as the tooltip, can be made language-
dependent by using the OEM text as text identifier under the "source" tag. The translation of
the text in the particular language is entered under the "translation" tag.
Entries Meaning
source Text identifier
See 1st example: Single-line text with new text identifier "MY_NEW_TEXT".
See 2nd example: Double-line text with new text identifier
"MY_NEW_TEXT_2_LINES".
translation Text, which is displayed on the user interface.
You can enter single and multi-line texts. "%n" is used to indicate a line break.
See 1st example: Single-line text "My new text" is displayed.
See 2nd example: Double-line text "My new - text" is displayed.
chars Text length
See 1st example: Text length of 30 characters is specified.
See 2nd example: Text length of 10 characters per line is specified.
lines Number of lines
See 2nd example: The number of rows is 2.
remark Own comments - are not displayed.
Procedure
1. You can copy the sample file "oem_sltmlistdialog_eng.ts" from the following directory: /
siemens/sinumerik/hmi/template/lng
2. Save the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory.
3. Change the file name to "sltmlistdialog_eng.ts".
If you wish to create texts for additional languages, then a separate file must be created
for each language. Save the file with the appropriate language code in the file name.
4. Open the file and define the texts in the <message> and </message> areas.
5. Restart the system.
The file must still be converted into a binary format in order that the texts are displayed
during the program runtime. This data is only converted during power up.
Text identifiers in tool details Text identifiers in tool details - all parameters
TM_HL_TOOL_USER_1_DETAILS to ...10_DETAILS TM_HL_TOOL_USER_1_LONG to ...10_LONG
TM_HL_TOOL_APPL_1_DETAILS to ...10_DETAILS TM_HL_TOOL_APPL_1_LONG to ...10_LONG
Text identifiers in tool details Text identifiers in tool details - all parameters
TM_HL_EDGE_USER_1_DETAILS to ...10_DETAILS TM_HL_EDGE_USER_1_LONG to ...10_LONG
TM_HL_EDGE_APPL_1_DETAILS to ...10_DETAILS TM_HL_EDGE_APPL_1_LONG to ...10_LONG
Text identifiers in tool details Text identifiers in tool details - all parameters
TM_HL_EDGE_SUPUSER_1_DETAILS to ...10_DETAILS TM_HL_EDGE_SUPUSER_1_LONG to ...10_LONG
TM_HL_EDGE_SUPAPPL_1_DETAILS to ...10_DETAILS TM_HL_EDGE_SUPAPPL_1_LONG to ...10_LONG
"MultiToolAppl_1" to "MultiToolAppl_10"
Text identifiers in tool details Text identifiers in tool details - all parameters
TM_HL_MULTITOOL_USER_1_DETAILS to ... TM_HL_MULTITOOL_USER_1_LONG to ...10_LONG
10_DETAILS
TM_HL_MULTITOOL_APPL_1_DETAILS to ... TM_HL_MULTITOOL_APPL_1_LONG to ...10_LONG
10_DETAILS
Example 2
A new parameter is configured in the following example from Section Configuring list
parameters (Page 161):
<PARAMETERCONFIGURATION>
<EdgeUser_1_Bit0>
<Base value="EdgeUser_1" type="QString" />
The two texts under HeadLine and ToolTip should be output depending on the language. To
do this, the two text identifiers must be included in the sltmlistdialog_xxx.ts file:
12.4 Examples
Example
"sltmlistconfig.xml" or "sltmturninglistconfig.xml" file:
Example
"sltmlistdialog_eng.ts" file:
</message>
<!-- **** Headline for own parameter *** -->
<!-- **** Priority tool *** -->
<message>
<source>TMO_HL_PRIOR_TOOL</source>
<translation>V</translation>
<remark>priority tool</remark>
<chars>1</chars>
<lines>2</lines>
</message>
<!-- **** Tooltip for own parameter *** -->
<!-- **** Priority tool *** -->
<message>
<source>TMO_TT_PRIOR_TOOL</source>
<translation>priority tool, %nuse tool preferably< /translation>
<chars>35</chars>
<lines>3</lines>
</message>
<!-- **** OEM cutting edge parameter 1 headline *** -->
<!-- **** Maximum tool width *** -->
<message>
<source>TM_HL_EDGE_USER_1</source>
<translation>maximum%nwidth</translation>
<chars>8</chars>
<lines>2</lines>
</message>
<!-- **** OEM cutting edge parameter 1 tooltip *** -->
<!-- **** Maximum tool width *** -->
<message>
<source>TM_TT_EDGE_USER_1</source>
<translation>maximum width%nof the tool%noverall</translation>
<chars>35</chars>
<lines>2</lines>
</message>
</context>
</TS>
Example
"sltmlistconfig.xml" or "sltmturninglistconfig.xml" file:
Example
"sltmlistdialog_eng.ts" file:
<source>TMMP_TT_HEAVY_TOOL</source>
<translation>heavy tool</translation>
<chars>35</chars>
<lines>2</lines>
</message>
<!-- **** Magazine location type 3 item *** -->
<!-- **** Big tool *** -->
<message>
<source>TMMP_TT_BIG_TOOL</source>
<translation>big</translation>
<chars>9</chars>
</message>
<!-- **** Magazine location type 3 tooltip *** -->
<!-- **** Big tool *** -->
<message>
<source>TMMP_TT_BIG_TOOL</source>
<translation>big tool</translation>
<chars>35</chars>
<lines>2</lines>
</message>
<!-- **** Magazine location type 4 item *** -->
<!-- **** Sensitive tool *** -->
<message>
<source>TMMP_ITEM_SENSITIVE_TOOL</source>
<translation>sensitive</translation>
<chars>9</chars>
</message>
<!-- **** Magazine location type 4 tooltip *** -->
<!-- **** Sensitive tool *** -->
<message>
<source>TMMP_TT_SENSITIVE_TOOL</source>
<translation>Notice: Tool can%nbe destroyed easily</translation>
<chars>35</chars>
<lines>2</lines>
</message>
</context>
</TS>
7RROKROGHU
[ :RUNSLHFHFRRUGLQDWH
V\VWHPZKHQ
/
VWWRROKROGHULVXVHG
/
/ 0'a/
]
:RUNSLHFHFRRUGLQDWH
V\VWHPZKHQ
QGWRROKROGHULVXVHG
[
7RROKROGHU
Due to the coordinate system being mirrored, the following machine/setting data must be set:
Note
The settings of MD10717 and MD15710 cannot be used if old G code programs are available
and will be used without modification for the second tool holder without mirroring of the X axis.
If transformation TRANSMIT is set up, the necessary mirroring can also be activated
automatically if programmed. For this, the TRANSMIT command must be replaced by a
subprogram (for example, in the manufacturer directory):
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[0]="TRANSMIT"
MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[1]="TRANSM"
Subprogram TRANSMIT.SPF:
PROC TRANSMIT(INT_NR)
F_T_REV2
TRANSM(_NR)
F_T_REV2
RET
Note
In the status display, TRANSM is now displayed instead of TRANSMIT.
General conditions
● The taper turning is not enabled for "working with two tool holders."
● The B-axis function (kinematics) is also not enabled for "working with two tool holders."
12.6.1 Overview
The tool management offers the possibility to define all real tool magazines and internal
magazines with the appropriate properties from the operating software and link them channel-
specific with the tool unit. You can configure the relationships between tool magazine, griper
and spindle via a tree view.
General sequence
The following steps are required to create a tool management:
● Create tool unit
● Define buffer locations
● Define loading location
● Create magazine configuration
● Link assignments
Note
When you create a new tool unit, a buffer location with a spindle location, a loading magazine
with a loading location and a real magazine with five locations are created by default.
Symbol Description
Folder for the actively used tool units
Folder with access to templates
Tool spindle / tool holder
Tool gripper 1
Tool gripper 2
Shows the changes in the the "Active data" folder that has not been activated yet
Procedure
Note
If you position the cursor on an element, only those functions possible for this element are
active. All other functions are inactive which is indicated with grayed-out softkeys.
Procedure
Editing an element
1. Position the cursor on the "Active data" folder element.
2. Navigate with the <Cursor right> and <Cursor down> keys to the element
that you want to edit.
4. Enter the desired changes and press the "OK" softkey to confirm the en‐
tries.
Note
You define the number of buffer and magazine locations in the input window of the higher-level
<Magazine> folder element with the "Locations" parameter.
Activating Data
1. Press the "Activate data" softkey.
All changed parameterizations are transferred to the NC and activated.
All of the error messages are displayed again, and you have the option
of specifically resolving these by modifying the data.
Note
Once you have made changes to the tool management, the data is marked with "*". This data
is not yet in the NC and so does not have any effect.
If you want to create a tool management that is similar to an already existing element, then
you can save time if you copy the existing elements and insert them at a different position.
You have the option, for example of also copying inactive subtrees into the active tree.
- OR -
Press the "Cut" softkey.
3. Position the cursor at the required position and press the "Paste" softkey.
If the element exists already at the desired location, you receive further
insertion options.
4. Press the "OK" softkey if you wish to attach the element to the tree view
as the next element.
The element is inserted.
Note:
You have the option of changing the name of the element in the associ‐
ated input window.
Deleting elements
1. Place the cursor on the desired element and press the "Delete element"
softkey.
Directory values
You are currently located under the "Active data" → <tool unit> directory in the "Commissioning"
→ "NC" →"Tool management" operating area.
You can set the following parameters in the "TO unit" window from the tool unit directory:
Parameters Description
Name Designation that is displayed in the tree structure.
Channel number The channel to which the tool unit is assigned.
Parameters Description
Tool search Search strategy:
● Without search strategy
● Active tool
● Shortest way
Empty location search Search strategy:
● Without search strategy
● First location forwards
● Current location forwards
● Current location backwards
● Last location backwards
● Symmetric current location
● 1:1 exchange
Directory values
You are currently located under the "Active data" → <tool unit> → <buffer> directory in the
"Commissioning" → "NC" →"Tool management" operating area.
You can define the following parameters in the "Magazine" window from the buffer directory:
Parameters Description
Name Designation of the buffer magazine
The designation is displayed in the tree structure.
Magazine number 9998 (cannot be changed)
Locations Number of the buffer locations
Element values
You can change the buffer location type with the parameters in the "Location" window:
Parameters Description
(Selection menu) Select a buffer type
● Tool spindle / tool holder
● Loader
● Gripper
● Transfer location
Index The index counts the locations of a type.
Directory values
You are currently located under the "Active data" → <tool unit> → <loading magazine> directory
in the "Commissioning" → "NC" →"Tool management" operating area.
You can define the following parameters in the "Magazine" window from the loading magazine
directory:
Parameters Description
Name Designation of the loading magazine
The designation is displayed in the tree structure.
Magazine number 9999 (cannot be changed)
Locations Number of loading locations
Element values
You can change the loading location type with the parameters in the "Location" window:
Parameters Description
(Selection menu) Select a loading location type:
● Load location
Load locations are areas on the machine at which the direct loading
in the magazine is possible. The tool can be inserted directly into
the magazine at this location. The magazine location to be loaded
is moved to the loading point. For example, chain magazines have
loading points.
● Loading station
A loading station is a location outside the magazine onto which the
tool to be loaded is placed. The tool is then transported from that
location to the magazine via a transport mechanism. Loading
stations are generally used for box or chain magazines.
Index The index counts the locations of a type.
Note
Loading point 1 is always set automatically as loading/unloading point for spindle 1 (manual
loading point).
Directory values
You are currently located under the "Active data" → <tool unit> → <magazine> directory in the
"Commissioning" → "NC" →"Tool management" operating area.
You can define the following parameters in the "Magazine" window from the magazine
directory:
Parameters Description
Magazine type Selection menu:
● Chain magazine
● Box magazine
● Revolver
Name Designation of the magazine.
The designation is displayed in the tree structure.
Magazine number Specifies the number of the magazine
Locations Number of magazine locations
Tool search Search strategy:
● Without search strategy
● Take from the TOA
● Active tool
● Shortest way
Empty location search Search strategy:
● Without search strategy
● Take from the TOA
● First location forwards
● Current location forwards
● Current location backwards
● Last location backwards
● Symmetric current location
● 1:1 exchange
Location coding ● Variable
● Fixed-location coded
Location type Identification for the magazine location type
(Changes the value globally for all locations in the magazine)
Consider adjacent location ● Yes
● No
(Changes the value globally for all locations in the magazine)
Note
If one of the Location type or Consider adjacent location parameters is changed individually
and the value is not identical for all locations, the "Variable" definition appears in the display.
Element values
You can change the magazine location type with the parameters in the "Location" window:
Parameters Description
Location type Identification for the magazine location type
Consider adjacent location ● Yes
● No
Element values
You are currently located under the "Active data" → <tool unit> directory in the "Commissioning"
→ "NC" →"Tool management" operating area.
You can link the following parameters with each other from the selection list via the
Assignments element:
● Spindle/gripper/loader for magazine
● Gripper/loader for spindle
● Loading point for magazine
Note
The separation as number of locations from the magazine zero point of the affected magazine
to the internal magazine location must be defined for each magazine assignment.
Example
If, for example, tools on a spindle must be replaced from a magazine, the following assignment
can result:
Magazine Magazine_1
Parameters Assignment
Spindle/gripper/loader for ● Tool spindle location 1 for magazine (separation 0)
magazine ● Gripper location 2 for magazine (separation 0)
● Gripper location 3 for magazine (separation 0)
● Transfer location 4 for magazine (separation 0)
Gripper/loader for spindle ● Tool spindle location 1 for gripper 2
● Tool spindle location 1 for gripper 3
Loading point for magazine ● Loading point location 1 for magazine (separation 0)
● Loading point location 2 for magazine (separation 3)
Storage
The text files are created in the directory:
/oem/sinumerik/hmi/lng
Procedure
9. If you have entered the alarms with the help texts, press the "OK" soft‐
key.
You will receive the message "The alarm texts have been saved and
converted."
The cursor jumps to the first entry of the selected alarm text file.
The cursor jumps to the last entry of the selected alarm text file.
See also
Range of alarms (Page 244)
13.2 Configuring alarm and message texts via alarm text files
You have the option of creating customized alarm and message texts using alarm text files
and adapting these.
The alarm texts are set up in standard format (".ts" format) by SINUMERIK Operate. The ".ts"
format is XML-based.
You can create and edit these files not only with SINUMERIK Operate, but also externally on
a PC.
Note
If you wish to edit alarm text files on a PC, use an editor supporting UTF-8 coding.
Note
Chinese alarm texts should only be implemented with character set GB2312.
Chinese logograms are not supported in Korean.
Example:
<!DOCTYPE TS>
<TS>
<context>
<name>slaeconv</name>
<message>
<source>700000/PLC/PMC</source>
<translation>First OEM alarm text</translation>
</message>
<message>
<source>700001/PLC/PMC</source>
<translation>Second OEM alarm text</translation>
</message>
</context>
</TS>
Example:
Note
The conversion is only made if the .ts file is newer than the associated .qm file.
Note
Explanation for the "Index identifier" string
● "<" ≙ opening pointed bracket "<"
● ">" ≙ closing pointed bracket ">"
Example
<!DOCTYPE TS>
<TS>
<context>
<name>my_context</name>
<message>
<source>1</source>
<translation>First OEM parameter text</translation
</message>
<message>
<source>2</source>
<translation>Second OEM parameter text</translation
</message>
</context>
</TS>
Example
Note
The conversion is only made if the .ts file is newer than the associated .qm file.
Example
<!DOCTYPE TS>
<TS>
<context>
<name>partprogmsg01</name>
<message>
<source>4711</source>
<translation>part program message No. 4711</translation
</message>
</context>
</TS>
Example
Example
Note
The conversion is only made if the .ts file is newer than the associated .qm file.
3. Enter the attribute name of the alarm color to be changed in the <Attribute AttrName=…>
tag. You can change the following colors:
– Font color of the alarm/message text = TEXTCOLOR
– Background color of the alarm/message text = TEXTBACKGROUNDCOLOR
– Font color of the alarm number = NUMBERCOLOR
– Background color of the alarm number = NUMBERBACKGROUNDCOLOR
4. Alarm sources are defined in the <Sources> area for whose alarms the alarm colors are to
be changed, e.g. the alarm sources "/HMI" and "/PLC/PMC".
Note
If you insert further alarm sources, make sure that the alarm number is always assigned to
the correct alarm source.
The possible values for source ID and URL can be found in the table in Section Range of
alarms (Page 244).
5. In the <Alarms> tag, create a separate sub-area for each alarm or for an alarm number
range.
6. Enter the alarm number in the <Alarm AlarmID= "..." > tag, or enter the alarm number range
in the <Range FromAlarmID="..." ToAlarmID= "..."> tag.
7. Enter the required color values in the following tags:
<TEXTCOLOR>
<TEXTBACKGROUNDCOLOR>
<NUMBERCOLOR>
<NUMBERBACKCOLOR>
The attributes of the color values are defined by specifying an RGB value:
– An RGB value always starts with the "#" character.
– The individual color values R, G and B are represented by double-digit hexadecimal
numbers. Syntax: "#RRGGBB", e.g. "#FF9A00".
Example
Note the order in the XML configuration file for the assignment of the colors to alarm number
ranges:
<AttrDescr>
Text color of an alarm used when displayed within the
header panel.
</AttrDescr>
</Attribute>
<Attribute AttrName="TEXTBACKGROUNDCOLOR" AttrID="5004"
AttrDataType="10">
<AttrDescr>
Background color of an alarm used when displayed within
the header panel.
</AttrDescr>
</Attribute>
<Attribute AttrName="NUMBERCOLOR" AttrID="5005"
AttrDataType="10">
<AttrDescr>
Text color of an alarm used when displayed within the
header panel.
</AttrDescr>
</Attribute>
<Attribute AttrName=" NUMBERBACKGROUNDCOLOR " AttrID="5006"
AttrDataType="10">
<AttrDescr> Background color of an alarm used when
displayed within the header panel.
</AttrDescr>
</Attribute>
</Attributes>
</Category>
</Type>
</Types>
<Sources>
<Source> CatLink="1" SourceID="10000" SourceURL="/HMI">
<Alarms>
<Alarm AlarmID="130000">
<TEXTCOLOR>#000000</TEXTCOLOR>
<TEXTBACKGROUNDCOLOR>#FFFFFF</TEXTBACKGROUNDCOLOR>
<NUMBERCOLOR>#FFFFFF</NUMBERCOLOR>
<NUMBERBACKGROUNDCOLOR>#000000</NUMBERBACKGROUNDCOLOR
</Alarm>
</Alarms>
</Source>
<Source> CatLink="1" SourceID="51" SourceURL="/PLC/PMC">
<Alarms>
<Range FromAlarmID="700100" ToAlarmID="700199">
<TEXTCOLOR>#000000</TEXTCOLOR>
<NUMBERCOLOR>#00FF00</NUMBERCOLOR>
</Range>
<Alarm AlarmID="700000">
<TEXTCOLOR>#000000</TEXTCOLOR>
<TEXTBACKGROUNDCOLOR>#FFFFFF</TEXTBACKGROUNDCOLOR>
<NUMBERCOLOR>#FFFFFF</NUMBERCOLOR>
<NUMBERBACKGROUNDCOLOR>#000000</NUMBERBACKGROUNDCOLOR
</Alarm>
</Alarms>
</Source>
</Sources>
</SlAeAlarmAttributes>
The result of the conversion is written to the file "oem_ae_database_conversion.log". This file
is located in the "/user/sinumerik/hmi/log" directory.
Note
The conversion is only carried out if the XML file is newer than the associated hmi file.
4. The <source> tag contains the alarm number of the standard alarm, e.g. 10000.
5. The <translation> tag contains the actual alarm text, e.g. "OEM alarm text example for NCK
alarm 10.000".
Example
<!DOCTYPE TS>
<TS>
<context>
<name>myNckAlarms</name>
<message>
<source>10000/NCK</source>
<translation> OEM alarm text example for NCK alarm 10.000</
translation>
</message>
</context>
<TS>
Example:
Note
A dedicated link must be created for each standard alarm for which the text is to be replaced.
Example
</Type>
</Types>
<Sources>
<Source CatLink="1" SourceID="0" SourceURL="/NCK">
<Alarms>
<Alarm AlarmID="10000">
<MSGTEXT>myNckAlarms|10000/NCK</MSGTEXT>
</Alarm>
</Alarms>
</Source>
</Sources>
</SlAeAlarmAttributes>
Note
The conversion is only made if the .ts file is newer than the associated .qm file.
SourceIDs 1 ... 10
The SourceIDs 1 ... 10 have the following relationship:
SourceID SourceURL
1 /NCK/Channel#1/Partprogram
2 /NCK/Channel#2/Partprogram
3 /NCK/Channel#3/Partprogram
4 /NCK/Channel#4/Partprogram
5 /NCK/Channel#5/Partprogram
6 /NCK/Channel#6/Partprogram
7 /NCK/Channel#7/Partprogram
8 /NCK/Channel#8/Partprogram
9 /NCK/Channel#9/Partprogram
10 /NCK/Channel#10/Partprogram
Parameter Description
specifier
%1 First parameter from the alarm data of the alarm source.
%2 Second parameter from the alarm data of the alarm source.
%3 Third parameter from the alarm data of the alarm source.
%4 Fourth parameter from the alarm data of the alarm source.
%5 Fifth parameter from the alarm data of the alarm source.
Only for NCK alarms:
First part (up to the separator) of the fourth parameter from the alarm data of the alarm
source.
Parameter Description
specifier
%7 Seventh parameter from the alarm data of the alarm source
Only for NCK alarms:
Third part (between the 2nd and 3rd separator) of the fourth parameter from the alarm
data of the alarm source.
%8 Eighth parameter from the alarm data of the alarm source
Only for NCK alarms:
Fourth part (between the 3rd and 4th separator) of the fourth parameter from the alarm
data of the alarm source.
%9 Ninth parameter from the alarm data of the alarm source.
%0 Tenth parameter from the alarm data of the alarm source.
%Z As for %1, in the case of S7-HiGraph alarms the step number of the graph is shown.
%K Specially for PLC alarms:
Second digit of the decimal alarm ID: 123456, corresponds to channel number (0 =
channel 10).
%A Specially for PLC alarms:
Third and fourth digit of the decimal alarm ID: 123456, corresponds to the axis number.
%N Specially for PLC alarms:
Fifth and sixth digit of the decimal alarm ID: 123456, corresponds to the signal number.
- OR -
Press the <INPUT> key.
Default
Per default, the alarm log contains all alarms and messages - with their incoming and outgoing
time stamps - in chronological order since the last boot. The exceptions are messages from
the NC part program (msg command).
Contrary to the "Alarm List" or "Messages" window, all of the alarms or messages that are no
longer active when the log is displayed are also displayed (historical alarm events).
NOTICE
Shorter CF card service life
If the alarm log is a continuously written to the CompactFlash card, then only a limited number
of write cycles is possible. Therefore, ensure that the storage is only performed when there
is a justifiable need! Undo the setting "at every event" if you no longer require that the alarm
log is saved.
The CompactFlash card has a service life of over 10 years for an average written data volume
of approx. 60 MB/day.
The alarm log is not saved in the default configuration.
Procedure
3. Open the file and enter the number of events to be output in the tag <Records type .../>.
The preset value is 500. The maximum number depends on the storage medium (hard disk
or CompactFlash card).
4. Enter the backup mode in the <DiskCare type="int" value="-1"/> tag. The following values
are possible:
-1: There is no backup of the alarm log (default setting).
0: Each alarm event triggers an immediate backup of the alarm log (persistency backup).
>0: Rhythm of the log saving in seconds: When there is a change, the log is time-triggered
saved every n > 0 seconds (persistency backup).
5. You adapt the filter for the entry type in the <Filter> tag. Please observe the following:
– An alarm event is only entered in the log when it satisfies the filter criterion.
– If several filters are specified in succession, they are linked by a logical OR.
– Several filters must be combined in series with the keyword AND for an AND operation.
Note
Each incoming or outgoing event of an alarm or message requires a separate entry, even when
they belong to the same alarm or message.
Acknowledgement events are also contained in the alarm log. You require such entries even
when these are presently not recognizable in the alarm log.
Filter properties
A filter consists of the following three elements <identification> <relation> <value>.
Cancel criteria
Examples
Log all alarms with a ClearInfo not equal to 15, i.e. no part program messages:
<CONFIGURATION>
<Protocol>
<Filters>
<Siemens_Filter_01 type="QString" value="CLEARINFO NOT 15" />
</Filters>
</Protocol>
</CONFIGURATION>
Log all alarms with the SourceURL "/NCK" or "/HMI":
<CONFIGURATION>
<Protocol>
<Filters>
<Filter_01 type="QString" value="SourceURL EQUAL /NCK" />
<Filter_02 type="QString" value="SourceURL EQUAL /HMI" />
</Filters>
</Protocol>
</CONFIGURATION>
In the <FilePath> tag, adapt the path and file name for the file in which the alarm log is stored
persistently:
<CONFIGURATION>
<Protocol>
<Filters>
<FilePath type="QString" value="$(HMI_INSTALL_DIR)user/
sinumerik/hmi/ log/alarm_log/slaepp_" />
</Filters>
</Protocol>
</CONFIGURATION>
● Path
Environment variables can also be incorporated in the path, e.g. for the installation directory:
$(HMI_INSTALL_DIR).
● File name:
A 3-digit number and the file extension "hmi" are automatically added to the specified file
name during operation, e.g. "slaepp_123.xml". The number is automatically increased
when:
– The file has reached the maximum size (DiskCare = 0), or
– The specified period has elapsed (DiskCare > 0).
Older files are deleted.
<CONFIGURATION>
<Protocol>
<Filters>
<Filter_00 type="QString" value="" />
<Filter_01 type="QString" value="CLEARINFO NOT 15 AND
AlarmID LOWER 700000"/>
<Filter_02 type="QString" value="CLEARINFO NOT 15 AND
AlarmID HIGHER 700200"/>
</Filters>
</Protocol>
</CONFIGURATION>
Result
For the changes to the protocol settings to take effect, restart SINUMERIK Operate.
Introduction
For alarms that are triggered via the PLC blocks SFC17 and SFC18, a parameter can be
transferred each time the block is called. If the "Octet string" data type is selected, up to 12
bytes can be transferred.
With an appropriate configuration of the operating software, a maximum of 12 bytes can be
interpreted, e.g. also as an array of bytes or as a structure with any order of simple data types.
In this way, several parameters can be displayed in the alarm text.
A parameter description must be stored for each alarm in the operating software. Two aspects
must be taken into account with this parameter description:
● How the parameter has to be interpreted correctly (data type and, if necessary, length)
● How the parameter has to be prepared for display (string or number, decimal, hexadecimal,
binary, etc.)
Point 1 is irrespective of the language selected for the display, point 2 can be different
depending on the national language.
The possible parameter descriptions are therefore divided into a language-independent
parameter statement and a language-dependent format statement and stored in the following
directories:
The names of the files can be freely selected. The parameter statement is added to the
configured data of the relevant alarm in the database in the form of the alarm attribute
"HMIPROPARAMDESCR2". Because of the language dependency, the format statement is
part of the alarm text.
Parameter statement
The parameter statement describes how one or more parameters can be defined with the
maximum 12-bytes long octet string supplied with the alarm PDU.
Syntax
The following syntax applies for the parameter statement:
Examples
Example of an alarm attribute file (how to create an alarm attribute file, see Changing alarm
attributes (Page 236)):
</Alarms>
</Source>
</Sources>
</SlAeAlarmAttributes>
Format statement
The format statement is part of the alarm text and is used as a placeholder for a parameters
to be displayed.
Syntax
The following syntax applies for the format statement:
Examples
@1%b@ → Value from the first parameter description to be displayed as a binary num‐
ber, e.g. "1011011"
@2%8X@ → Value from the second parameter description to be displayed as a hexadec‐
imal number with eight digits, missing digits are filled with 0, e.g. "00AF37FE"
@1%7.2f@ → Value from the first parameter description to be displayed as a fixed point
number with seven digits (incl. sign and decimal point) and two digits after
the decimal point, missing digits are filled with 0, e.g. "-012.34"
Example of an alarm text file (how you create alarm texts, see Creating in-house alarm texts
(Page 228)):
<!DOCTYPE TS>
<TS>
<context>
<name>my_oem_plc_alarms_context</name>
<message>
<source>700000/PLC/PMC</source>
<translation>Text with three BYTE parameters: @1%X@, @2%u@, @3%b@</translation>
</message>
<message>
<source>700001/PLC/PMC</source>
<translation>Text with three WORD parameters: @1%X@, @2%u@, @3%b@</translation>
</message>
<message>
<source>700002/PLC/PMC</source>
<translation>Text with three 16-bit INTEGER parameters: @1%X@, @2%u@, @3%b@</translation>
</message>
<message>
<source>700003/PLC/PMC</source>
<translation>Text with four parameters: @1%X@, @2%u@, @3%r@, @4%b@</translation>
</message>
</context>
</TS>
You can copy this area from the original file. The "slaesvcadapconf.xml" file is in the following
directory: /siemens/sinumerik/hmi/base
Setting
In the <MissingTextWarning type="bool" value="FALSE"/> tag, deactivate/activate the
warning.
Entry Meaning
TRUE The warning is displayed.
FALSE The warning is deactivated.
Example
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CONFIGURATION>
<ControlFlags>
<MissingTextWarning type="bool" value="FALSE"/>
</ControlFlags>
</CONFIGURATION>
Software option
You require the "Collision avoidance (machine, working area)" software option in
order to use this function.
Machine manufacturer
Please refer to the machine manufacturer's specifications.
Collision avoidance is based on a machine model. The kinematics of the machine are
described as a kinematic chain. For machine parts, which are to be protected, protection areas
are attached to these chains. The geometry of the protection areas is defined using protection
area elements. The control then knows how they move in the machine coordinate system
depending on the position of the machine axes. You then subsequently define the collision
pairs, i.e. two protection areas, which are monitored with respect to one another.
The "Collision avoidance" function regularly calculates the clearance from these protection
areas. When two protection areas approach one another, and a specific safety clearance is
reached, an alarm is displayed and before the corresponding traversing block, the program is
stopped and/or the traversing motion is stopped.
Note
Start-up of a machine model
You require access level 1 (manufacturer) for creating and editing a machine model.
Note
The collision monitoring is only valid for single-channel machines.
Note
Referenced axes
The positions of the axes in the machine area must be known so that the protection areas can
be monitored. For this reason, the collision avoidance is only active after the referencing.
NOTICE
No complete machine protection
Incomplete models, e.g. machine parts, workpieces that have not been modeled or new
objects in the working area, are not monitored and can therefore cause collisions.
Collision detection
The detection of a risk of collision is controlled via the following criteria:
● Collision tolerance
The collision tolerance defines the accuracy of the tool modeling. You must note that an
increase in the accuracy reduces the performance.
● Safety clearance
The safety clearance sets the minimum clearance that must exist.
For better visualization, you can assign different colors to the various model parts. If there is
a risk of a collision, at least one collision pair is highlighted in color.
During simultaneous recording, the active machine model is shown in addition to the
simultaneous recording graphic.
References
More detailed explanations of collision avoidance can be found in the following reference:
Special Functions Function Manual:
● Section: "Kinematic chain (K7)"
● Section: "Geometric machine modeling (K8)"
● Section: "Collision avoidance (K9)"
● Section: "NC/PLC interface signals (Z3)" > "Collision avoidance (K9)"
Enable function
Set the following machine data item in order to enable the function:
Parameter assignment
Note
If a specific safety clearance has been set for a collision pair via the system variable
$NP_SAFETY_DIST, this has priority over the NC-specific safety clearance set in the
MD10622 $MN_COLLISION_SAFETY_DIST machine data.
Signal Meaning
DB10.DBX58.0 - 7 Collision avoidance: Deactivate protection area group
DB10.DBX234.0 - DBX241.7 Collision avoidance: Activate protection area
Note
The $NP_BIT_NO protection area can be assigned to an arbitrary bit number of the
DB10.DBX234.0 - DBX241.7 interface signals.
The following setting is a prerequisite: $NP_INIT_STAT == "P" (preactivated or PLC controlled)
References
Machine Data and Parameters List Manual
Procedure
Procedure
Copying/cutting/pasting elements
If you want to create a kinematic or protection area element that is similar to an already existing
element, then you can save time if you copy the element and insert it at a different position.
You have the option, for example of also copying inactive subtrees into the active tree.
- OR -
Press the "Cut" softkey.
3. Position the cursor at the required position and press the "Paste" softkey.
4. Press the "OK" softkey if you wish to attach the element to the chain as
the next element.
The element is inserted and the name is automatically extended by a long
underscore and incremented.
Note:
You have the option of changing the name of the element in the associ‐
ated input window.
- OR -
Press the "Parallel" softkey if you wish to insert the element parallel to the
selected element.
Note:
The “Parallel” softkey is not available for protection areas.
Note
Inserting the same element
If you insert the same element, then this is automatically inserted in front of the selected
element.
Deleting elements
1. Place the cursor on the desired element and press the "Delete element"
softkey.
2. Press the "OK" softkey to confirm the deletion.
The selected object is removed.
All subsequent elements are moved into the "Free elements" folder.
- OR -
If the selected element is linked with additional elements, which are also
to be deleted, then press the "With successors" softkey.
Note
Deleting a machine model
If you select the "Active data" folder in the tree view, and press the "Delete elements" softkey,
and confirm the subsequent prompt with "OK", the machine model is deleted with all elements
and protection areas.
If you do not wish to remove the STL files, then cancel delete with "No" to the prompt "3D files".
Precondition
● You are in the graphic machine model editor.
● The "Graphic" and "Autozoom" softkeys are active.
Procedure
- OR -
Press the "Zoom -" softkey if you wish to reduce the size of the section.
- OR -
Press the "Auto zoom" softkeys if you wish to automatically adapt the
segment to the size of the window.
The automatic scaling function takes into account the largest expansion
of the model.
Note
Selected section
The selected sections and size changes are kept as long as the program is selected.
Note
Mouse operation
Using the mouse wheel, you have the option of shifting the model in the graphic view.
Requirement
● You are in the graphic machine model editor.
● The "Graphic" and "Autozoom" softkeys are active.
Procedure
- OR -
Press the "Magnify -" or <-> softkey to reduce the frame.
- OR -
Press one of the cursor keys to move the frame up, down, left or right.
Requirement
● You are in the graphic machine model editor.
● The "Graphic" and "Autozoom" softkeys are active.
Procedure
3. Press the "Arrow right", "Arrow left", "Arrow up", "Arrow down", "Arrow
clockwise" or "Arrow counter-clockwise" softkey to change the position of
the machine model.
...
...
- OR -
Press the <Cursor right>, <Cursor left>, <Cursor up> or <Cursor down>
key to move the machine model.
- OR -
Keep the <Shift> key pressed and rotate the machine model in the desired
direction using the appropriate cursor keys.
Note
Working with a mouse
Using a mouse, you have the option of rotating and shifting the model in the graphic view.
● Move the model with the left-hand mouse key pressed to shift the model.
● Move the model with the right-hand mouse key pressed to rotate the model.
Precondition
● You are in the graphic machine model editor.
● The "Graphic" and "Autozoom" softkeys are active.
Procedure
2. Press the "From front" softkey if you wish to view the machine model from
the front.
- OR -
Press the "Side view" softkey if you wish to view the machine model from
the side.
- OR -
Press the "Top view" softkey if you wish to view the machine model from
the top.
Precondition
● You are in the graphic machine model editor.
● The "Graphic" and "Autozoom" softkeys are active.
Procedure
The machine model with all display and monitoring elements is displayed
in the graphics window.
- OR -
Press the "Detail level -" softkey to display the next lower detail level.
Note
One of the two display versions is always active!
Kinematic elements
The following elements are available to create the kinematic chain:
● Rotation and parallel rotation
● Linear axis and parallel linear axis
● Rotary axis and parallel rotary axis
● Offset and parallel offset
● Switch and parallel switch
coordinate axes are arranged in the positive traversing direction of the machine linear main
axes.
Requirement
● The option is set.
● The machine data is set.
Procedure
3. Position the cursor to the "Active data" folder and press the "New element"
and "Kinematic element" softkeys.
The "New kinematic element" selection window opens.
4. For example, select the "Offset" element and press the "OK" softkey.
The "Offset" window opens to define the shift vector.
The first element of the kinematic chain can be an offset, a rotation, a
linear axis or also a rotation axis.
5. Press the "OK" softkey to insert the element.
See also
Kinematic rotation and parallel kinematic rotation (Page 270)
Linear axis and parallel linear axis (Page 271)
Rotary axis and parallel rotary axis (Page 272)
Offset and parallel offset (Page 272)
Switch and parallel switch (Page 273)
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Rotary axis (X) X component of the vector, around which the system rotates.
Rotary axis (Y) Y component of the vector, around which the system rotates.
Rotary axis (Z) Z component of the vector, around which the system rotates.
Angle of rotation Angle, around which the system rotates in the direction of the rotation
vector.
See also
Creating a kinematic chain element (Page 269)
Dynamic linear axes are identified by this symbol in the tree topology.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Axis (X) X component of the direction vector
Axis (Y) Y component of the direction vector
Axis (Z) Z component of the direction vector
Axis name Specification of the axis identifier (see MD 10000)
Axis offset Additive offset between the actual position of the axis, and the value
used by the collision monitoring.
See also
Creating a kinematic chain element (Page 269)
Dynamic rotation axes are identified by this symbol in the tree topology.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Rotary axis (X) X component of the vector, around which the system rotates.
Rotary axis (Y) Y component of the vector, around which the system rotates.
Rotary axis (Z) Z component of the vector, around which the system rotates.
Axis name Specification of the axis identifier (see MD 10000)
Axis offset Additive offset between the actual position of the axis, and the value
used by the collision monitoring.
See also
Creating a kinematic chain element (Page 269)
Static offset vectors are designated by this symbol in the tree topology.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Offset (X) X component of the direction vector.
Offset (Y) Y component of the direction vector.
Offset (Z) Z component of the direction vector.
See also
Creating a kinematic chain element (Page 269)
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Number Index of the switch in a kinematic chain (default = -1, the switch is
switched on constantly).
Position Value at which the switch is to be switched on.
See also
Creating a kinematic chain element (Page 269)
Note
Tool carriers are not modeled
Tool carriers, clamping or cutting edge holders are not emulated in the machine modeling and
are not checked for collision.
Precondition
● The option is set
● Machine data is set
● A kinematic chain has been created
Procedure
1. Position the cursor at the kinematic chain element to which you wish to
attach a protection area.
2. Press the "New element" softkey.
See also
Tool protection area (Page 274)
Machine protection area (Page 275)
Note
For the automatic tool protection area, a spindle must exist in the channel.
Note
Attaching a tool protection area
"Frame" type tool protection area elements may be attached to tool protection areas.
Tool protection areas are identified by this symbol in the tree topology.
Element values
Parameter Meaning
Name Designation that is displayed in the tree structure.
Color Selection of the color
Detail level Defines from which detail level the protection area or the protection area
elements are displayed on the user interface.
● Lowest detail level: 0
● Highest detail level: 3
PLC bit Only for pre-activation
● -1
Not activated
● 0 - 63
Activation of the collision avoidance is controlled using the bit
entered here.
The maximum number of PLC bits depends on MD18897. It can be
a maximum of 64.
See also
Creating protection areas (Page 273)
Machine protection areas are identified by this symbol in the tree topology.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Color Selection of the color
Detail level Defines from which detail level the protection area or the protection area
elements are displayed on the user interface.
● Lowest detail level: 0
● Highest detail level: 3
PLC bit Only for pre-activation
● -1
Not activated
● 0 - 63
Activation of the collision avoidance is controlled using the bit
entered here.
The maximum number of PLC bits depends on MD18897. It can be
a maximum of 64.
Activation ● Activated
Activates the collision avoidance for the protection area.
● Deactivated
Deactivates the collision avoidance for the protection area.
● Preactivated
Activation of the collision avoidance is controlled using the bit
entered into the "PLC bit".
See also
Creating a kinematic chain element (Page 269)
Creating protection areas (Page 273)
Note
Parallel protection area elements
You have the possibility of creating two protection area elements in parallel in a hierarchic level
of the tree structure. This means that parallel elements have the previous element as the same
origin.
To create two elements in parallel with one another at one level, use a "parallel" element.
If you create an additional protection area element, then this is shifted into the next level.
Preconditions
● A kinematic chain has been created
● The cursor is on a protection area (machine or tool protection area) or at a protection area
element.
Procedure
3. Select the required basic form (e.g. box to model a table) and press the
"OK" softkey.
The corresponding window to enter the element values opens.
4. Define the values and press the "OK" softkey to confirm the entries.
See also
Frame and parallel frame protection area element (Page 278)
Box and parallel box protection area elements (Page 279)
Sphere and parallel sphere protection area elements (Page 281)
File and parallel 3D file protection area element (Page 284)
Cylinder and parallel cylinder protection area element (Page 282)
Note
A work offset or coordinate rotation affects all the following protection area elements.
Coordinate system transformations are identified by this symbol in the tree top‐
ology.
Element values
Parameter Meaning
Name Designation that is displayed in the tree structure.
Offset (X) X component of the direction vector.
Offset (Y) Y component of the direction vector.
Offset (Z) Z component of the direction vector.
Rotary axis (X) X component of the rotation vector.
Rotary axis (Y) Y component of the rotation vector.
Rotary axis (Z) Z component of the rotation vector.
Angle of rotation The value by which the system rotates around the rotation vector.
See also
Creating protection area elements (Page 276)
]
+ \
[
%
/
Y
=
Y
<
;
:HOWNRRUGLQDWHQV\VWHP
V1 Sum of the offset and rotation between this element and the root element.
V2 Offsets and rotation from the parameters of this element.
Box-shaped protection area elements are identified by this symbol in the tree
topology.
Element values
Parameter Meaning
Name Designation that is displayed in the tree structure.
Color
Selection of the color for the protection area element.
● Activate the checkbox "From protection area", if the color of the
associated tool and/or machine protection area should be applied.
Deactivate the checkbox "From protection area" in order to select
any color.
● Select the required color from the selection list.
Detail level Defines from which detail level the protection area or the protection area
elements are displayed on the user interface.
● Activate the checkbox "From protection area", if the detail level of
the associated tool and/or machine protection area should be
applied.
Deactivate the checkbox "From protection area", if you wish to
define your own detail level for the element.
● Enter the desired level of detail:
– Lowest detail level: 0
– Highest detail level: 3
Parameter Meaning
Use ● Display
The protection area element is shown in the graphic view.
The element is only visible if the "Display model" softkey is active.
The element is not monitored for collision.
● Monitoring
The protection area element is used for the collision avoidance.
The element is only visible if the "Monit. model" softkey is active.
● Display and monitoring
The protection area element is used for display in the graphic view
and for collision avoidance.
The element is visible in both display versions.
Length (X) Length of the cube in the X direction.
Width (Y) Width of the cube in the Y direction.
Height (Z) Height of the cube in the
Z direction.
Offset (X) X component of the direction vector.
Offset (Y) Y component of the direction vector.
Offset (Z) Z component of the direction vector.
Rotary axis (X) X component of the rotation vector.
Rotary axis (Y) Y component of the rotation vector.
Rotary axis (Z) Z component of the rotation vector.
Angle of rotation The value by which the system rotates around the rotation vector.
See also
Creating protection area elements (Page 276)
<
;
5
Y
=
Y
<
;
:HOWNRRUGLQDWHQV\VWHP
V1 Sum of the offset and rotation between this element and the root element.
V2 Offsets and rotation from the parameters of this element.
Sphere-shaped protection area elements are identified by this symbol in the tree
topology.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Color Selection of the color for the protection area element.
● Activate the checkbox "from protection area", if the color of the
associated tool and/or machine protection area should be applied.
Deactivate the checkbox "from protection area" in order to select
any color.
● Select the required color from the selection list.
Detail level Defines from which detail level the protection area or the protection area
elements are displayed on the user interface.
● Activate the checkbox "from protection area", if the detail level of
the associated tool and/or machine protection area should be
applied.
Deactivate the check box "from protection area", if you wish to define
your own detail level for the element.
● Enter the desired level of detail:
– Lowest detail level: 0
– Highest detail level: 3
Parameter Meaning
Use ● Display
The protection area element is shown in the graphic view.
The element is only visible if the "Display model" softkey is active.
The element is not monitored for collision.
● Monitoring
The protection area element is used for the collision avoidance.
The element is only visible if the "Monit. model" softkey is active.
● Display + monitoring
The protection area element is used for display in the graphic view
and for collision avoidance.
The element is visible in both display versions.
Radius Specification of the radius
Offset (X) X component of the direction vector.
Offset (Y) Y component of the direction vector.
Offset (Z) Z component of the direction vector.
Rotary axis (X) X component of the rotation vector.
Rotary axis (Y) Y component of the rotation vector.
Rotary axis (Z) Z component of the rotation vector.
Angle of rotation The value by which the system rotates around the rotation vector.
See also
Creating protection area elements (Page 276)
File and parallel 3D file protection area element (Page 284)
<
;
5
Y
=
Y
<
;
:HOWNRRUGLQDWHQV\VWHP
V1 Sum of the offset and rotation between this element and the root element.
V2 Offsets and rotation from the parameters of this element.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Color Selection of the color for the protection area element.
● Activate the checkbox "from protection area", if the color of the
associated tool and/or machine protection area should be applied.
Deactivate the checkbox "from protection area" in order to select
any color.
● Select the required color from the selection list.
Detail level Defines from which detail level the protection area or the protection area
elements are displayed on the user interface.
● Activate the checkbox "from protection area", if the detail level of
the associated tool and/or machine protection area should be
applied.
Deactivate the check box "from protection area", if you wish to define
your own detail level for the element.
● Enter the desired level of detail:
– Lowest detail level: 0
– Highest detail level: 3
Parameter Meaning
Use ● Display
The protection area element is shown in the graphic view.
The element is only visible if the "Display model" softkey is active.
The element is not monitored for collision.
● Monitoring
The protection area element is used for the collision avoidance.
The element is only visible if the "Monit. model" softkey is active.
● Display + monitoring
The protection area element is used for display in the graphic view
and for collision avoidance.
The element is visible in both display versions.
Height (Z) Height of the cylinder in the
Z direction.
Radius Specification of the radius
Offset (X) X component of the direction vector.
Offset (Y) Y component of the direction vector.
Offset (Z) Z component of the direction vector.
Rotary axis (X) X component of the rotation vector.
Rotary axis (Y) Y component of the rotation vector.
Rotary axis (Z) Z component of the rotation vector.
Angle of rotation The value by which the system rotates around the rotation vector.
See also
Creating protection area elements (Page 276)
Note
Coordinate origin
The coordinate origin of the file does not have to match the coordinate system of the machine.
You align the coordinate system using offsets and rotations.
;
<
Y
=
Y
<
;
:HOWNRRUGLQDWHQV\VWHP
V1 Sum of the offset and rotation between this element and the root element.
V2 Offsets and rotation from the parameters of this element.
Element values
Parameter Meaning
Name Designation, which is displayed in the tree structure.
Color Selection of the color for the protection area element.
● Activate the checkbox "from protection area", if the color of the
associated tool and/or machine protection area should be applied.
Deactivate the checkbox "from protection area" in order to select
any color.
● Select the required color from the selection list.
Detail level Defines from which detail level the protection area or the protection area
elements are displayed on the user interface.
● Activate the checkbox "from protection area", if the detail level of
the associated tool and/or machine protection area should be
applied.
Deactivate the check box "from protection area", if you wish to define
your own detail level for the element.
● Enter the desired level of detail:
– Lowest detail level: 0
– Highest detail level: 3
Parameter Meaning
Use ● Display
The protection area element is shown in the graphic view.
The element is only visible if the "Display model" softkey is active.
The element is not monitored for collision.
● Monitoring
The protection area element is used for the collision avoidance.
The element is only visible if the "Monit. model" softkey is active.
● Display + monitoring
The protection area element is used for display in the graphic view
and for collision avoidance.
The element is visible in both display versions.
File name Name of the file with the description of the protection area element in
STL format.
Offset (X) X component of the direction vector.
Offset (Y) Y component of the direction vector.
Offset (Z) Z component of the direction vector.
Rotary axis (X) X component of the rotation vector.
Rotary axis (Y) Y component of the rotation vector.
Rotary axis (Z) Z component of the rotation vector.
Angle of rotation The value by which the system rotates around the rotation vector.
See also
Creating protection area elements (Page 276)
Sphere and parallel sphere protection area elements (Page 281)
Precondition
A kinematic chain has been created and includes valid protection areas.
Procedure
1. Position the cursor in the tree view on the "Collision groups" folder.
The "New collision element" selection window opens.
2. Select "Collision pair" and press the "OK" softkey.
3. Enter the values and press the "OK" softkey to confirm the entries.
See also
Collision pair (Page 287)
Element values
Parameter Meaning
1. Area Designation of the first protection area that is to be monitored.
2. Area Designation of the second protection area that is to be monitored.
Safety clearance Defining the safety clearance:
● 0
For the safety clearance, the value that has been defined in
MD10622 is taken.
● >0
The value that you entered here is used for the safety clearance.
Note
In order that the defined protection areas are checked for collision, they must be activated and
the collision avoidance activated.
See also
Creating a collision pair (Page 286)
Tool changes
If, in a machine model, tools change as a result of being replaced/exchanged or wear without
programming a tool offset selection (D number), then the recalculation of the machine model
must be explicitly requested. You will find more precise information in:
Function Manual Special Functions (FB3); collision avoidance (K9),
Chapter: "Function description" > "Tools"
14.8.1 Fundamentals
General Information
The following example contains the machine model elements of a simple 3-axis milling
machine for a simplified kinematic chain.
6WDQG
=D[LV
<
7RROKROGHU =
<
; ;
7RRO
0DFKLQH]HUR
7DEOH
5HIHUHQFHSRLQW
The following elements are defined for the example of the 3-axis milling machine:
Geometry
Each machine-model element has a defined geometry and an offset vector to the element
center starting with the machine zero:
9=$
96
9722/
=
97
ෘ <
;
The following offset vectors are defined for the example of the 3-axis milling machine:
*HRPHWULFPDFKLQHPRGHOLQJ
7 7RROKROGHU
722/ 0$&+,1( =D[LV
3URWHFWLRQDUHDV 0$&+,1(
.LQHPDWLFFKDLQ
=D[LV
$;,6B/,1
Offset
1. Mark the "Active data" folder and press the "New element" softkey.
A selection window with kinematic elements opens.
2. Select the "Offset" kinematic element and press the "OK" softkey.
The appropriate input window for the element values opens in the lower
part of the tree view.
3. Enter the required values:
Name: ROOT
Offset (X): 0
Offset (Y): 0
Offset (Z): 0
4. Press the "OK" softkey to save the values.
- OR -
Press the "Cancel" softkey to close the input window.
1. Mark the "ROOT" kinematic element and press the "New element" soft‐
key.
A selection window with kinematic elements opens.
2. Select the "Linear axis" kinematic element and press the "OK" softkey.
The appropriate input window for the element values opens in the lower
part of the tree view.
3. Enter the required values:
Name: X axis
Axis (X): 1
Axis (Y): 0
Axis (Z): 0
Axis name: X1
Axis offset: 0
4. Press the "OK" softkey to save the values.
- OR -
Press the "Cancel" softkey to close the input window.
1. Mark the "X axis" kinematic element and press the "New element" softkey.
A selection window with kinematic elements opens.
2. Select the "Linear axis" kinematic element and press the "OK" softkey.
The appropriate input window for the element values opens in the lower
part of the tree view.
3. Enter the required values:
Name: Y axis
Axis (X): 0
Axis (Y): 1
Axis (Z): 0
Axis name: Y1
Axis offset: 0
4. Press the "OK" softkey to save the values.
- OR -
Press the "Cancel" softkey to close the input window.
1. Mark the "X axis" kinematic element and press the "New element" softkey.
A selection window with kinematic elements opens.
2. Select the "Parallel linear axis" kinematic element and press the "OK"
softkey.
The appropriate input window for the element values opens in the lower
part of the tree view.
3. Enter the required values:
Name: Z axis
Axis (X): 0
Axis (Y): 0
Axis (Z): 1
Axis name: Z1
Axis offset: 0
4. Press the "OK" softkey to save the values.
- OR -
Press the "Cancel" softkey to close the input window.
1. Mark the "ROOT" kinematic element and press the "New element" soft‐
key.
2. Press the "Collision element" softkey.
3. In the "New collision element" window, select the collision element "Ma‐
chine protection area" and press the "OK" softkey.
4. Enter the following values:
Name: Stand
Color: Gray
Detail level: 0
PLC bit: -1
Activation: Activated
5. Press the "OK" softkey to save the values.
1. Mark the "Stand" machine protection area and press the "New element"
softkey.
2. Select the "Box" protection area element and press the "OK" softkey.
1. Mark the "Y axis" kinematic element and press the "New element" softkey.
3. Select the "Machine protection area" collision element and press the "OK"
softkey.
4. Enter the following values:
Name: Table
Color: Green
PLC bit: -1
Detail level: 0
Activation: Activated
5. Press the "OK" softkey to save the values.
1. Mark the "Table" machine protection area and press the "New element"
softkey.
2. Select the "Box" protection area element and press the "OK" softkey.
1. Mark the "Z axis" kinematic element and press the "New element" softkey.
3. Select the "Machine protection area" collision element and press the "OK"
softkey.
4. Enter the following values:
Name: Z axis
Color: Gray
Detail level: 0
PLC bit: -1
Activation: Activated
5. Press the "OK" softkey to save the values.
1. Select the "Z axis" machine protection area and press the "New element"
softkey.
2. Select the "Box" protection area element and press the "OK" softkey.
1. Mark the "Z axis" kinematic element and press the "New element" softkey.
3. Select the "Machine protection area" collision element and press the "OK"
softkey.
4. Enter the following values:
Name: Tool holder
Color: Blue
Detail level: 0
PLC bit: -1
Activation: Activated
5. Press the "OK" softkey to save the values.
1. Mark the "Tool holder" machine protection area and press the "New ele‐
ment" softkey.
2. Select the "Cylinder" protection area element and press the "OK" softkey.
1. Mark the "Z axis" kinematic element and press the "New element" softkey.
3. In the selection box, select "Tool protection area" collision element and
press the "OK" softkey.
4. Enter the following values:
Name: T
Color: red
Detail level: 0
PLC bit: -1
Activation: Activated
TO unit: 1
Magazine: 9998.
Location: 1
5. Press the "OK" softkey to save the values.
1. Mark the "Collision groups" folder and press the "New element" softkey.
A selection window for the collision element opens.
2. Select the "Collision pair" collision element and press the "OK" softkey.
The appropriate input window for the element values opens in the lower
part of the tree view.
3. Enter the required values:
1st range: T
2nd range: Table
4. Press the "OK" softkey to save the values.
- OR -
Press the "Cancel" softkey to close the input window.
1. Mark the "Collision groups" folder and press the "New element" softkey.
A selection window for the collision element opens.
2. Select the "Collision pair" collision element and press the "OK" softkey.
The appropriate input window for the element values opens in the lower
part of the tree view.
3. Enter the required values:
1st range: Tool holder
2nd range: Table
4. Press the "OK" softkey to save the values.
- OR -
Press the "Cancel" softkey to close the input window.
There are various ways of creating and reloading archives via the SINUMERIK Operate user
interface.
● Standard archive: Data can be selected specifically in the data tree and backed up by
pressing the "System data" softkey.
● Start-up archive: The "Start-up archive" softkey offers the following selection:
– Create and read-in a start-up archive
– Create PLC hardware upgrade archive (only SDBs)
– Create and read in archive of original status
Storage locations
Archives can be stored in the following directories:
● CompactFlash card at: System CF-Card/user/sinumerik/data/archive or System CF-Card/
oem/sinumerik/data/archive
● PCU: F:hmisl\user\sinumerik\data\archive or \oem\sinumerik\data\archive
● All configured logical drives (USB, network drives)
Note
USB FlashDrive
USB-flash drives are not suitable as persistent memory media.
Overview
A start-up archive can be generated, for example, after the control has been commissioned.
To do this, control components can be saved individually or jointly. It is also possible to transfer
the backed-up data to other controls so that they can be updated to the same status.
Note
When generating the start-up archive, programs that have been moved outside the system
(network drive) and any global part program memory that has been set up are not taken into
account. Only the programs from the NC memory and the local drive are archived.
Requirement
You require at least access level 2 (service).
Procedure
8. Position the cursor at the required storage location, press the "Search"
softkey and enter the required search term in the search dialog. Then
press the "OK" softkey if you wish to search for a certain directory or
subdirectory.
Note: The place holders "*" (replaces any character string) and "?" (re‐
places any character) make it easier for you to perform a search.
- OR -
Select the required storage location, press the "New directory" softkey,
enter the required name in the "New Directory" window and press the
"OK" softkey to create a directory.
NOTICE
Loss of additional languages during software upgrade
All the system languages are overwritten during software upgrades. If there are more
languages in the system than in the upgrade archive, these additional languages are lost
when the archive is read in. It is not possible to back up the languages before software
upgrade.
Note
The reading in of a start-up archive with drive configurations results in the overwriting of the
drives in the logdrive.ini file. The system creates a backup copy with the name logdrive_ini.sav
or logdrive.oldstyle. Before the archive is read in, the new drive configurations are activated.
Note
To prevent the NCU from shutting down unintentionally, you must disable all energy saving
profiles before you read in a start-up archive. For more detailed information about the energy
saving profiles topic, see:
Operating Manuals for SINUMERIK Operate, Chapter "Ctrl Energy".
Requirement
You require at least access level 2 (service).
Procedure
- OR -
Press the "No overwriting" softkey if you wish to keep existing files.
- OR -
Press the "Skip" softkey if you only wish to overwrite certain files.
You will then obtain a "Read error log for archive" in which the skipped or
overwritten files are listed.
8. Press the "Cancel" softkey to cancel the read-in process.
Procedure
Requirement
In order to save NC data, you require access level 2 (service).
To back up programs/workpieces, you require access level 6 (keyswitch position 1).
Procedure
Precondition
You require access level 2 (service).
Procedure
4. Activate the "Read in archive of original status" checkbox and press the
"OK" softkey.
SINUMERIK Operate automatically accesses the "original.arc" file.
A window opens prompting whether you want to perform a start-up.
5. Press the "OK" softkey.
The read-in process is started and a progress message box is displayed
in the window.
Any errors that occur are then displayed in the "Write Error Log for Ar‐
chive" window.
Procedure
1. Insert the storage medium in the USB port.
2. Press the key combination <Ctrl> + <Alt> + S.
All data required for diagnostics are compiled in an archive. Operator control is not possible
while the archive is being generated.
3. You will receive a message once archiving has been completed.
The system assigns an archive name and this is: CompletArchiv<Date>_<Time>.arc.
The dialog box is closed and you can re-operate the control.
Reading-out archives
The files to be sent (directories or individual files) are zipped in an archive (*.arc). If you send
an archive (*.arc), this is sent directly without being additionally zipped. If you have selected
an archive (*.arc) together with an additional file (e.g. directory), then these are zipped into a
new archive and are then sent.
Reading-in archives
Only archives can be read-in via the V24 interface. These are transferred and then
subsequently unzipped.
Note
Start-up archive
If you read in a start-up archive via the V24 interface, then this is immediately activated.
Procedure
1. Select the "Program manager" operating area, and press the "NC"
or "Local drive" softkey.
...
- OR -
Select the "Startup" operating area and press the "System data"
softkey.
Reading-out archives
2. Select the directories or the files that you wish to send via V24.
3. Press the ">>" and "Archive" softkeys.
- OR -
Reading in an archive
Press the "V24 receive" softkey if you wish to read-in files via V24.
Procedure
RS-232-C settings
Parameter Meaning
Protocol The following protocol is supported for transfer via the RS-232-C:
● RTS/CTS
Transfer It is also possible to use a secure protocol for data transfer (ZMODEM
protocol).
● Normal (default setting)
● Secure
For the selected interface, secure data transfer is set in conjunction
with handshake RTS/CTS.
Parameter Meaning
Baud rate Transfer rate: Transfer rates of up to 115 kbaud can be selected. The
baud rate that can be used depends on the connected device, the cable
length and the general electrical conditions.
● 110
● ....
● 19200 (default setting)
● ...
● 115200
Archive format ● Punched tape
● Binary format (PC format)
RS-232-C settings (details)
Interface ● COM1
● COM2 only relevant for SINUMERIK Operate on PC
Parity Parity bits are used for error detection: The parity bits are added to the
coded characters to make the number of positions set to "1" an uneven
number (uneven parity) or to an even number (even parity).
● None (default setting)
● Odd
● Even
Stop bits Number of stop bits for asynchronous data transfer.
● 1 (default setting)
● 2
Data bits Number of data bits for asynchronous data transfer.
● 5 bits
● ...
● 8 bits (default setting))
XON (hex) Only for punched tape format
XOFF (hex) Only for punched tape format
End of data transfer (hex) Only for punched tape format
Stop with end of data transfer character
The default setting for the end of data transfer character is (HEX) 1A.
Time monitoring (sec) Time monitoring
For data transfer problems or at the end of data transfer (without end of
data transfer character) data transfer is interrupted after the specified
number of seconds.
The time monitoring is controlled by a time generator (clock) that is star‐
ted with the first character and is reset with each transferred character.
The time monitoring can be set (seconds).
MD11280 $MN_WPD_INI_MODE
Processing mode of ini files in the workpiece directory
= 1 When the NC is started for the first time, after the workpiece selection, ini files with the name
of the selected part program and the following extensions are executed:
CEC Sag compensation (Cross Error Compensation)
GUD User data (Global User Data)
PRO Protection zones
RPA R parameters
SEA Value assignments (Setting Data Active)
TMA Magazine data (Tool Magazine Active)
TOA Tool offsets (Tool Offset Active)
UFR Work offsets (User Frame)
Activate
By default, the network settings cannot be backed up. The archiving of the network settings
must be enabled:
1. Copy the "slpmconfig.ini" file from the /siemens/sinumerik/hmi/template/cfg directory.
2. Store the file in the /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg directory.
3. Open the file and enter the following for [SeriesSetup]:
SupportNetworkSettings=true
4. Restart SINUMERIK Operate.
Note
This setting also affects the creation of a complete standard archive using Ctrl+Alt+S or Ctrl
+Alt+C.
Restrictions
● The leases files are not saved:
– /system/etc/udhcpd-eth0.leases
– /system/etc/udhcpd-ibn0.leases
● A configuration in the system network must be based on the DNS name rather than IP
addresses.
Basic procedure
● Backup of network settings
After activation, the network settings can also be backed up when a commissioning archive
is created when a check mark is set, see Creating a start-up archive (Page 300).
● Importing network settings
The saved archives can be imported in the same manner as a commissioning archive, see
Reading-in a start-up archive (Page 302).
Note
Importing network settings for replacement components
Disconnect the replacement components from the system network before you import the
saved network settings.
NCU
Only the NCU settings are saved with the HMI on the NCU. The following data is backed up:
● /user/system/etc/basesys.ini
● /user/common/tcu (complete directory)
The network settings of an NCU can be backed up and read only from an HMI on the PC/PG.
This means the NC address in mmc.ini on the PC/PG is always 192.168.215.1.
PCU
PCU and, if applicable, NCU settings saved with the HMI on the PCU. The following data is
backed up:
● PCU
– /user/system/etc/basesys.ini
– mmc.ini for SINUMERIK Operate
● NCU (when present as master)
– /user/system/etc/basesys.ini
– /user/common/tcu (complete directory)
The following archives are created: Archivename_pcu.arc and Archivename_ncu.arc
Importing an archive for a configuration with NCU as master (DHCP) and PCU (on_low):
1. Import the archive for Archivename_pcu.arc on a PCU with SINUMERIK Operate.
2. Depending on the replaced parts of the NCU, note the following:
– If the NCU was not replaced, the system restarts.
– The NCU has been replaced, Archivename_ncu.arc must be imported via the X127
interface with a separate HMI.
Procedure
See also
Settings of the system network (Page 316)
Settings of the factory network (Page 319)
Saving network settings (Page 321)
Setting Description
DHCP activated Activates or deactivates the DHCP mode for the
system network. This automatically assigns IP ad‐
dresses to the nodes in the system network.
DHCP server synchronization mode Activates or deactivates the DHCP server synchro‐
nization mode. If this setting is active, then the
DHCP servers synchronize themselves in the sys‐
tem network (X120) so that only one of them ac‐
tively assigns addresses. This makes it possible
to operate multiple NCUs or PCUs concurrently
without having to adjust the network settings.
The DHCP servers that are not active go into
"standby" mode; in this mode they regularly get the
current address data and TCU data from the active
server so that if the active server fails, a standby
server can take over the active role without data
loss.
● The Master priority setting influences the
synchronization so that the server with the
"Master" setting is always the active server (it
must be active in the network).
Deterministically the same control is then
always the DHCP server and the current
address and TCU data can be found there.
Master priority must only be set for a single
DHCP server in the system network.
● The settings Low priority and High priority can
be used to specify which DHCP server takes
precedence as the active server. A DHCP
server with low priority is then only used as
active server when a server with high priority
cannot be found in the network.
Default: High priority
DHCP address range Specifies the range for DHCP addresses. The
range starts at the address specified at Start and
ends at the address entered at End. The resulting
range of numbers has the following default setting:
Start address = first address in the system network
End address = start address + 10 or + 2 (if less
than 16 addresses are available)
Setting Description
Timeout when waiting for master Specifies a maximum waiting time (in seconds) for
the response of the master server (see DHCP
server synchronization mode). After this time elap‐
ses, the server itself becomes the active server.
This additional pause makes it possible for the in‐
tended DHCP master to become the active DHCP
server without displacement even if it is shortly
switched on thereafter, or takes longer to boot than
other controls.
Default: 120 seconds
Host name Assigns the DHCP server a fixed host name. In
this way, the server can also be addressed via the
host name and not only via the IP address.
Because the host name is also used as DNS
name, it must satisfy the corresponding require‐
ments of the RFC:
● ASCII letters (a-z, A-Z), digits (0-9) and '-'
● maximum 63 characters
DNS domain This is used to specify the Top Level Domain (TLD)
name used in the system network. The DNS server
of the NCU assigns names to the devices in the
system network in this zone. Name requests for all
other zones are forwarded to an external name
server in the company network.
The "local" default setting recommended by the
RFC1035 is used for local networks, to avoid con‐
flicts with globally defined domain names. As a
rule, this default setting is sufficient.
PN station name A separate machine name can be defined here for
PROFINET purposes. This is used at the ERTEC
interface (when available), transferred to the ER‐
TEC system program and also used by DCP at this
network interface.
Station name This string is used for the SINUMERIK-specific
OID mcSinumerikMIB.mcSinumerikMiscStation.
The value is the name of a station to which the
device belongs. Devices with the same station
name can therefore be identified as belonging to‐
gether. This is for information purposes only.
Location This string is used for the standard OID SNMPv2-
MIB::sysLocation. If required, a location can be
specified here which can be called by an SNMP
client. This is for information purposes only.
Contact person This string is used for the standard OID SNMPv2-
MIB::sysContact. If required, a contact address
can be specified here which can be called by an
SNMP client. This is for information purposes only.
Setting Description
Function This string is used for the Siemens Industry-spe‐
cific OID automationSystemIdent.automation‐
FunctionTag. If required, a function designation
can be specified here which can be called by an
SNMP client. This is for information purposes only.
Fixed domain Defines an additional DNS domain name (suffix for
DNS queries). This is of especial interest when the
DHCP server is switched off at the X120 because
this cannot set the "local" domain, but it is required
for some DNS queries (e.g. for machine control
panels).
Fixed DNS servers Specifies up to three DNS servers that are to be
used by the DHCP server. This is of especial in‐
terest when the DHCP server is switched off at the
X120 because this is also a DNS server or deter‐
mines DNS servers in the network.
Routing
● Routing X120/X127 -> X130 Specifies whether the routing of packets from the
system network (X120) and/or service connection
X127 to the company network (X130) is active:
● Enabled: Activates the routing for X120 and
X127
● Disabled: Deactivates the routing for X120 and
X127
● X127: Activates only the routing from X127 to
the company network
● X120: Activates only the routing from the
system network to the company network
● Routing X127 -> X120 Activates or deactivates the NAT routing of pack‐
ets from the service connection X127 to the sys‐
tem network (X120).
● Routing X120 -> X127 Activates or deactivates the routing of packets
from the system network (X120) to the service
connection X127. This is normally prohibited by
the firewall.
Note that there is no NAT and the sender must
ensure that packets to the PG or service PC at
X127 with address 192.168.215.x actually reach
the NCU to which the device is connected.
Active protocols Specifies which protocols are to be used in the
system network. DCP (Discovery and Basic Con‐
figuration Protocol) and LLDP (Link Layer Discov‐
ery Protocol) are available for selection. The ap‐
propriate active protocol is also used for the serv‐
ice connection X127 at the NCU.
Procedure
4. Press the "Reset DHCP server" softkey to return the current settings of
the DHCP server to the original settings.
5. Press the "Distribute DHCP data" softkey to synchronize the settings with
all nodes in the system network.
Note
You can only use the "Reset DHCP server" and "Distribute DHCP data" softkeys with a
connection to the active DHCP server.
Setting Description
Gateway If this value is not empty, the host specified there
is used as the default gateway, which means that
all IP packets that cannot be directly assigned are
sent there for routing.
DNS server If DNS name servers are specified here (maximum
three), then they must be used to resolve symbolic
host names, i.e. at most of the points where an IP
address is expected, a computer name can also
be used instead.
The name server setting is also sent to its DHCP
clients (TCU, PG) via the DHCP server of the NCU,
so that they can also work with symbolic names.
Time server Here you can specify up to three NTP servers
(UDP/123) that can be used by the NTPD on the
NCU for time synchronization.
Setting Description
Host name Here you can define a name for the local host. This
manually assigned name takes priority over all oth‐
er names.
The host name is determined in the following order:
● This entry (identical to the host name from the
basesys.ini file)
● A name received from the DHCP server
(reverse DNS lookup, i.e. which name belongs
to the received IP address)
● Default name ("NONAME_...")
Because the host name is also used as DNS
name, it must satisfy the corresponding require‐
ments of the RFC:
● ASCII letters (a-z, A-Z), digits (0-9) and '-'
● maximum 63 characters
Active protocols Specifies which protocols are to be used in the
company network. DCP (Discovery and Basic Con‐
figuration Protocol) and LLDP (Link Layer Discov‐
ery Protocol) are available for selection.
Firewall exceptions You can specify ports here that are to be enabled
in the external network interface.
● S7 communication (TCP/102) Port for the S7 communication
● VNC access (TCP/5900) Port for the VNC access
● Additional ports Any further ports can be enabled here. The entry
starts with the protocol name (TCP or UDP), fol‐
lowed by a slash '/' and the port number of the
service to be enabled. Several entries are separa‐
ted by a space.
Example (enabling of the VNC servers): TCP/
5900 TCP/5904 TCP/5905
NOTICE
Security risk
Note that opening the ports in the firewall can represent a security risk. Only enable the ports
that you actually require.
Note that every accessible service can have security gaps.
Procedure
Procedure
1. The network overview is open and you have made network settings.
- OR -
Press the "OK" softkey to save the network configuration.
Column Description
Consecutive number to identify the operator panel
Status Status of the operator panel:
: The operator panel is available on the bus.
: The operator panel is not available on the bus.
HW Information on the hardware of the operator panel
Possible values are unknown (no information available), NCU, PCU, PPU, TCU (all TCU
including HT 8, etc.).
Default value: Unknown
Name Name of the operator panel
MCP DIP switch position for the machine control panel
The values can be freely selected from 1 to 254 (0 means that the last active machine
control panel is retained, 255 means that a machine control panel is not being used).
Default value: 192
DCK Availability of direct control keys
Active: The TCU has direct control keys
Inactive: The TCU has no direct control keys
TCU Index for the TCU (Thin Client Unit)
The value is freely configurable from 0 to 255 and is used for identification in the PLC.
EKS DIP switch position for the chip reader for access levels (Electronic Key System)
Possible values range from 1 to 255. The value 0 means that an EKS is not used.
Virtual key‐ Use of a virtual keyboard
board Possible values are "Never", "Always" and "Auto", whereby "Auto" is set as default value.
Note
The information of the operator panels is read-only and cannot be changed in the OPs window.
The active DHCP server that contains the data for the operator panels can be a different NCU,
but also the local NCU itself. Irrespective of this, a copy of the data is stored and used on the
local NCU.
Procedure
Note
You can only use the "Distribute TCU data" softkey with a connection to the active DHCP
server.
Column Description
Consecutive number to identify the VNC connection
VNC server IP address or name of the NC
Displacement Specifies whether it is possible that the TCU will be displaced by other nodes.
/Priority Displacement priority: Specifies the priority which influences whether the TCU will be
displaced by other nodes.
The possible values lie between 0 and 10. The smaller the value, the faster the TCU
will be displaced. If the displacement is blocked, the priority will be ignored.
Start Specifies whether the TCU is to be started active, i.e. as operator panel.
/Priority Start-up priority: Specifies the priority of the TCU connection to be used.
Any value greater than 0 is permitted. The larger the value, the lower the connection
priority.
Column Description
Display area Specifies which HMI screen is displayed when activating the TCU.
Channel Specifies which channel is displayed when activating the TCU.
- OR -
4. Press the "Remove" softkey to remove a selected VNC connection from
the list.
- OR -
5. Press the "Move up" or "Move down" softkey to move a VNC connection
within the list.
- OR -
Press the "Cancel" softkey to cancel the changes.
See also
Displaying the available operator panels (Page 322)
softkeys in the channel menu, the switchover targets themselves (HMI, NC channel) are
displayed on the vertical softkeys assigned to a channel group.
Procedure
2. Select the required operator panel and press the "T:M:N" softkey
A list for the linking of the HMI softkeys to configured channel groups is
displayed in the lower part of the window.
3. Press the "Change" softkey.
The list can be edited.
4. Make the required change and press the "OK" softkey.
- OR -
Press the "Cancel" softkey to cancel the changes.
See also
Displaying the available operator panels (Page 322)
Error analysis
You have the option of initiating a fault analysis for the components involved. You obtain the
result of a such a diagnostics in the form of a fault message. The possible fault states and
causes are described in this fault message together with how to resolve the fault.
Detailed view
You have the option to display the following information about a selected component.
TCU
● IP address
● SW version
● MCP index from the configuration
● TCU index from the configuration
● DNS name
● Resolution
MCP
● IP address
● DNS name
● MCP index from the configuration
● MCP index requested from HMI
● MCP index requested from PLC
Procedure
2. Press the menu forward key and the "Bus TCP/IP" softkey.
7. Press the "Return" softkey in order to exit the "TCP/IP diagnostics" win‐
dow and return to the "PROFIBUS diagnostics" window.
Precondition
Error analysis only functions for a PCU.
Procedure
Remedy 5.1
Establish a physical connection.
16.6.2.5 The TCU cannot establish a network connection to the assigned PCU
System network
On the system network, process data communication and image transmission of the
components are executed with the operating software for the display units (TCUs).
A TCU and NCU are connected to the system network via Ethernet interface X120.
A PCU is connected via the ETH2 Ethernet adapter.
Company network
The company network is used, for example, to access the network drives.
An NCU is connected to the company network via Ethernet interface X130.
A PCU is connected via the ETH1 Ethernet adapter.
Availability
The availability describes the percentage of faulty packages compared to all the sent and
received packages.
Problems in the company network (e.g. logical drives that cannot be accessed, double IP
address, etc.) as well as settling time during power up can result in fluctuations in availability.
Green Greater than 95%
Yellow 50 - 95%
Red Less than 50%
● Computer name
● DNS name
Computer name of the controller as stored at the DNS server (Domain Name Service).
● MAC address
Physical address of the network adapter
● Address type
Information about the configuration of the network adapter in the configuration file
"basesys.ini":
– DHCP: DHCP is active for this network adapter.
The information behind the hyphen "-" specifies the DHCP mode of operation:
off - DHCP is deactivated for this adapter
Client - a DHCP client that receives an IP address and further data from a server, is
running on the interface
Server - the NCU provides a DHCP server on this interface that supplies clients on this
network with IPs
Synced Server - a protocol is active with which several NCUs synchronize with each
other. This ensures that always only one of these NCUs functions as DHCP server and,
for example, no double IP addresses
are assigned.
If a network adapter operates as "Synced Server", the "State of sync. DHCP server" line
displays additional information.
If no changes have been made for the network adapters in the configuration file, then
"Default" is also output.
– Manual
The settings IP address, subnet mask, DNS server 1, DNS server 2 and gateway are
configured in the "basesys.ini".
Note:
In the "Change" mode, either "Manual" or "DHCP" can be selected (only for company
network, X130).
● IP address assigned
Current IP address of the network adapter.
● Subnet mask assigned
● DHCP server
IP address of the network adapter (for address type "DHCP").
● State, DHCP server
State of the synch. DHCP server:
– Active (actual NCU is active in the group of all NCUs in the "Synced Server" mode and
transfers the IP addresses);
– Standby (NCU is not active, if the active server fails, this NCU could take over the task
of the server).
● Mode, DHCP synchron.
Priority of the synch. DHCP server:
Low, High, Master
● DNS server 1, DNS server 2
Domain Name Server
● Gateway
● Note
All information that is not available is marked in the relevant table line with a hyphen "-".
Modifiable parameters
The following parameters of the company network adapter (X130) can be set by selecting the
"Address type":
● Address type
● IP address
● Subnet mask
● DNS server 1 and 2
● Gateway (applies for system and company network)
Address types
● DHCP
The values for the settable parameters IP address, subnet mask, DNS server 1, DNS server
2 and gateway are defined automatically by the DHCP server, in accordance with the entry
in the "basesys.ini".
● Manual
The values for the settable parameters IP address, subnet mask, DNS server 1, DNS server
2 and gateway can be specified manually; these are then stored in the "basesys.ini".
References
For additional information about network configuration, please refer to the following
documentation:
SINUMERIK 840D sl, Operator Components and Networking (IM5)
Procedure
2. Press the menu forward key and the "Bus TCP/IP" softkey.
5. Enter the desired changes and press the "OK" softkey to confirm the
entries.
6. Press the "New display" softkey to refresh the display.
Procedure
2. Press the menu forward key and the "Bus TCP/IP" softkey.
- OR -
Press the "DHCP server" softkey to fetch information and query the status
of the DHCP server.
The "DHCP Server" window opens.
For each active DHCP server, the status, the role (priority), the MAC
address, the TCU version and the lease version are displayed in tabular
form in the upper part of the window. The required IP with the associated
address area appears in the lower part of the window.
Any differing data is displayed in red.
6. Press the "Address list" softkey to acquire all information about the active
DHCP server.
The "Address list" window is opened.
The IP address, the client ID in the form of the MAC address or the CF
card number, the lease version, the device number, the DNS name and
additional information are displayed for each node in a tabular form.
Inactive nodes are grayed out.
16.6.4.2 Messages
All the system-relevant state and error messages from the "syslog" log file are displayed via
the "Messages" softkey.
Procedure
If network problems occur, you can record the data traffic as a log file for analysis and
evaluation via the "Network Trace" window.
General information
● The function is protected with the standard password NETWORK
Note
Change the standard password to prevent improper use.
● The log is recorded via the tcpdump program (Linux) or the windump program (Windows).
Further information can be found at www.tcpdump.org
Requirement
If you want to change the password, you require access level 1 (manufacturer).
Procedure
- OR -
4. If required, parameterize the recording conditions in the "Parameters
(tcpdump)" input field.
5. Press the "Start" softkey to record the log.
Note: Recording stops automatically after 20 minutes.
6. Press the "Stop" softkey to complete the recording.
The "Export Trace File" window opens.
7. Select a storage location, assign a file name and confirm with "OK".
The trace file is moved to the storage location. With "Cancel", the log
remains in the following directory:
HMI data/Logs/Network trace/tcpdump.pcap or windump.pcap
8. If the log already exists, press the "Export trace file" softkey to save the
current log file, for example, on a USB.
The "Select Storage Location" window opens.
9. Select a storage location, assign a file name and confirm with "OK".
Change password
Trace parameters
You can parameterize the conditions for the log recording via the "Parameters (tcpdump)" input
field in the Network Trace window.
Syntax
<switch> <option>
<switch> parameters
Value Meaning
-D Displays a list of all network interfaces. All other <Switch> parameters
are ignored.
-i <interface> Defines which network interface has to be checked.
-n Host names are not resolved.
-c <number> The recording is stopped after a defined number of packets.
-C <file size> Limits the file size. When the file size is reached, a new file with name
and consecutive number, starting with 1, is created. The unit of the file
size corresponds to million bytes.
-e Outputs the Ethernet header.
-q Creates an abbreviated log version.
-vv Creates more detailed packet information.
-S Changes the packet sequence number from absolute to relative.
-A Outputs the contents of a packet as ASCII.
-xx Outputs the contents of a packet as Hex.
-XX Outputs the contents of a packet as Hex and as ASCII.
-s <bytes> Specifies the packet size in bytes that has to be recorded per packet.
The default is 68 bytes.
Note
The value -w is always implicitly contained in the call for the creation of the standard log file:
HMI data/Logs/Network trace/tcpdump.pcap or windump.pcap
Parameter <option>
Reference
Further parameter assignments can be found at www.tcpdump.org
Examples
Note
Although handheld terminals and EKS identification systems are not determined for the list of
accessible nodes, they can be added as additional nodes to the topology.
Procedure
4. Press the "By name", "By IP", "By type" or "By location" softkeys to sort
the display.
- OR -
3. Press the "Topology" softkey if you require an overview of all of the net‐
worked nodes, e.g. to check if there are connection problems.
The "Network Topology" window opens.
The interface, port and the actual connection are displayed for each node
using a tree topology.
Note: The station name must be defined for all nodes so that the topology
is correctly displayed.
4. Press the "Expand all" or "Close all" softkey to maximize or minimize the
tree topology.
5. Press the "Follow connection" softkey to follow nodes in the structure tree
using the marked line.
- OR -
3. If further information is provided for a selected node, press the "Details"
softkey to open the Web user interface.
Note: The installed operating software must be located in the same net‐
work as the device to be displayed. If necessary, this is achieved by the
assignment of a second IP address (alias).
The "Details" window opens.
4. Press the "Zoom +" or "Zoom -" softkey until the desired display size is
reached.
Additional nodes
3. Press the "Additional nodes" softkey to search for nodes that are not listed
under "Accessible nodes".
The "Search for Additional Nodes" window opens. If necessary, change
the address range and confirm with "OK".
The found nodes are appended in the table; the HW-Id/type, Location,
Contact and Description fields can then be edited and, by activating the
checkbox, added to the first column, and, with a subsequent save, added
to the reference topology.
Comparing
3. Press the "Compare" softkey to compare the current list of nodes either
with the previously saved manufacturer topology, a reference topology
or a saved topology in the .xml format.
The "Compare with" window opens. Position the cursor on the desired
option box and confirm with "OK".
Saving
Note
Manufacturer topology and reference topology can be created with access level 3 (user) or
higher and are always saved on the active DHCP server.
WARNING
Incorrect parameterization
Changes in the states of NC/PLC variables have a considerable influence on the machine.
Incorrect configuration of the parameters can endanger life and cause damage to the machine.
In the "NC/PLC Variables" window, enter the NC system variables and PLC variables that you
want to monitor or change in the list:
● Variable
Address for NC/PLC variable.
Incorrect variables have a red background and are displayed with a # character in the value
column.
● Comment
Any comment on the variable.
The columns can be displayed and hidden.
● Format
Specify the format in which the variable is to be displayed.
The format can be specified (e.g. floating point).
● Value
Displays the actual value of the NC/PLC variables.
PLC variables
Inputs Input bit (Ex), input byte (EBx), input word (EWx), input double word (EDx)
Outputs Output bit (Ax), output byte (ABx), output word (AWx), output double word
(ADx)
Bit memory Memory bit (Mx), memory byte (MBx), memory word (MWx), memory double
word (MDx)
Times Time (Tx)
Counters Counter (Cx)
Data Data block (DBx): Data bit (DBXx), data byte (DBBx), data word (DBWx),
data double word (DBDx)
Formats
B Binary
H Hexadecimal
D Decimal without sign
+/-D Decimal with sign
F Floating point (for double words)
A ASCII character
Notation examples
Permissible notation for variables:
● PLC variables: EB2, A1.2, DB2.DBW2
● NC variables:
– NC system variables: Notation $AA_IM[1]
– User variables / GUD: Notation GUD/MyVariable[1,3]
– OPI notation: /CHANNEL/PARAMETER/R[u1,2]
Inserting variables
The start value for "Filter/Search" of variables differs. For example, to insert the variable $R[0],
enter the following start value:
● The start value is 0 if you filter according to "System variables".
● The start value is 1 if you filter according to "All (no filter)". In this case, all signals are
displayed and shown in the OPI notation.
The GUD from the machine data is only displayed in the Search window for the variable
selection when the associated definition file has been activated. Otherwise, the sought
variables must be entered manually, e.g. GUD/SYG_RM[1]
The following machine data is representative for all variable types (INT, BOOL, AXIS, CHAR,
STRING): MD18660 $MN_MM_NUM_SYNACT_GUD_REAL
Note
Display of NC/PLC variables
● System variables can be dependent on the channel. When the channel is switched over,
the values from the selected channel are displayed.
● For user variables (GUD), it is not necessary to make a specification according to global
or channel-specific GUD. The first element of a GUD array starts with index 0 as for NC
variables.
● Using the tooltip, you can display the OPI notation for NC system variables (except for
GUD).
Servo variables
Servo variables can only be selected and displayed at "Diagnostics" → "Trace".
- OR -
1. Select the "Startup" operating area.
8. Press the "Change" softkey if you would like to edit the value.
The "Value" column can be edited.
9. Press the "Insert variable" softkey if you wish to select a variable from a
list of all existing variables and insert this.
The "Select Variable" window opens.
10. Press the "Filter/search" softkey to restrict the display of variables (e.g.
to mode group variables) using the "Filter" selection box and/or select the
desired variable using the "Search" input box.
Press the "Delete all" softkey if you would like to delete the entries for the
operands.
11. Press the "OK" softkey to confirm the changes or the deletion.
- OR -
Press the "Cancel" softkey to cancel the changes.
Changing operands
Depending on the type of operand, you can increment or decrement the address by 1 place
at a time using the "Operand +" and "Operand -" softkeys.
Note
Axis names as index
For axis names, the "Operand +" and "Operand -" softkeys do not act as index, e.g. for
$AA_IM[X1].
Examples
DB97.DBX2.5
Result: DB97.DBX2.6
$AA_IM[1]
Result: $AA_IM[2]
MB201
Result: MB200
/Channel/Parameter/R[u1,3]
Result: /Channel/Parameter/R[u1,2]
Procedure
1. You have entered values for the desired variables in the "NC/PLC varia‐
bles" window.
2. Press the ">>" softkey.
Enable displays
● On/Off1
● Off2
● Off3
● From the drive: Operation enabled
● From the infeed: Enable operation
● Enable pulses
● Speed controller enable NC
● Enable pulses
● Drive ready
● Heat sink temperature
● Power section in i2t limiting
● Motor temperature
● Measuring system 1 active / measuring system 2 active
The states for measuring system 1/2 have the following meaning:
Symbol Meaning
The position measuring system is active.
Procedure
Note
The following selection configurations have been previously defined, and cannot be changed
or deleted:
● All NC axes and drives
● NC axes
● Drives without NC axis assignment
Selection overview
The following information is provided in the selection overview.
Column Description
Bus No. Bus number for drives without NC assignment.
No entry for NC axes.
Slave address Slave address for drives without NC assignment.
No entry for NC axes.
Device No. Device number for drives without NC assignment.
No entry for NC axes.
Drive object No. Drive object number for drives without NC assignment.
No entry for NC axes.
Name/identifier For NC axes contains the standard machine axis identifier and the
user-defined machine axis names.
For drives without NC assignment, contains the drive object names.
Assignment NC is displayed for an internal object assignment.
PLC is displayed for an external object assignment.
Note
The selection overview differs in the information provided regarding the slave address and
device number between PROFIBUS and PROFINET configuration.
Procedure
No axis/drive is selected.
All axes are selected, which are defined in a minimum of one channel.
10. Press the "Delete selection" softkey to delete the actual selection.
11. Press the "Edit selection" softkey to edit the actual selection.
The "Edit selection" window opens.
12. If you click the "Back" softkey, you will return to the "Service Overview"
main screen.
Application
The following information is displayed in the "Service Overview" window:
● Check of the setpoint branch (e.g. programmed position setpoint, speed setpoint, spindle
speed setpoint)
● Check of the actual value branch (e.g. actual position value, measuring system 1 or 2,
actual speed value)
● Optimization of the position control loop of the axis (e.g. following error, control deviation,
servo gain factor)
● Check of the entire control loop of the axis (e.g. through position setpoint/actual-value
comparison and speed setpoint/actual-value comparison)
● Check of hardware errors (e.g. by checking the encoder: If the axis is moved mechanically,
the actual position value must change)
● Setting and check of the axis monitoring functions.
Procedure
- OR -
Press the "Axis selection" softkey.
The "Axis Direct Selection" window opens.
Select the required axis directly from those available in the drop-down list
box.
6. Confirm the selection with "OK".
The values of the axis are displayed.
Display data
6SHHGVHWSRLQW
.YIDFWRU
)ROORZLQJHUURU
>PPLQ@
8QLWIRUGHIDXOWVHWWLQJ
>PP@
● Active MS referenced
● Active MS must be referenced
Procedure
- OR -
Overview
The individual status displays, warnings, messages, etc. that are displayed in the "Service
Drive" window are explained in the following.
Further information about the interface signals can be found in the following documentation:
Function Manual, Basic Functions:
● Section "Various NC/PLC interface signals and functions (A2)"
● Chapter "NC/PLC interface signals (Z1)"
Further information about the drive parameters can be found in the following documentation:
List Manual, SINAMICS S120/S150 (Drive Object SERVO)
Pulses enabled
The message whether the pulses have been enabled for the drive corresponds to the interface
signal:
DB31, ... DBX93.7 "Pulses enabled".
Drive ready
The display of the current status of the selected drive corresponds to the interface signal:
DB31, ... DBX93.5 "Drive ready".
Ramp-up phase
The display of the current ramp-up phase of the selected drive corresponds to the drive
parameter:
r0002 "Drive operating display".
Note
If the display shows a value other than "0", please contact your Siemens regional office!
Motor temperature
The display of the current temperature in the motor corresponds to the drive parameter:
r0035 "Motor temperature"
Unit: °C
Integrator disabling
The display as to whether the integrator of the speed controller is active, corresponds to the
interface signal:
DB31, ... DBX93.6 "n-controller integrator disabled".
Parking axis
Displays (yes/no) whether it is a parking axis/spindle.
Note
With parking axes/spindles, all encoder-specific monitoring and evaluation functions are
switched off. This allows the encoder to be withdrawn without initiating an alarm.
Operating mode
The display of the control type of a drive corresponds to the drive parameter:
p1300[0…n] "Open-loop/closed-loop control mode".
Depending on "n", the following "values" are displayed:
n Display
20 Speed control (without encoder)
21 Speed control (with encoder)
23 Torque control (with encoder)
Motor temperature
The display of whether the motor temperature is OK corresponds to the interface signal:
DB31, ... DBX94.0 "Motor temperature prewarning".
References
Diagnostics Manual
Note
The utilization evaluation of the synchronized actions is only displayed when the value in
MD11510 $MN_IPO_MAX_LOAD ≠ 0.
Procedure
Procedure
Copy file
3. Open the folder specified above, and select the required screenshots.
4. Press the "Copy" softkey.
- OR -
Press the "Cut" softkey.
5. Open the required archive directory, e.g. on a USB flash drive and press
the "Paste" softkey.
Note
You can also copy the screenshots using "WinSCP" to a Windows PC.
Note
If you wish to view the screenshots, then you can open the files in SINUMERIK Operate. On
a Windows PC, you can open the data using a graphic program, e.g. "Office Picture Manager".
You save the machine information and address information in the "identSNAPSHOT" window.
You can either manually enter the data or import it from selection files.
Machine information
Entries Meaning
Machine No. The unique machine number (serial number of the CompactFlash card) is dis‐
played in the header. This number serves as information only and cannot be
changed.
Machine name The manufacturer assigns a unique machine number in this field which is stored
in machine data MD17400 $MN_OEM_GLOBAL_INFO.
Note: The machine name is a mandatory field. No data can be stored until this
field is completed.
Machine type Machine type.
Address information
Under Addresses you can enter the following data for the manufacturer/manufacturer's
regional office, dealer and end customer:
● Customer number
● Manufacturer name and, if required, Branch name / Dealer name / End user name
● Street, Postal code/ZIP code, Location, Country (can be selected from a selection list),
Region/State
● Address of contact: Name, Phone, Fax, E-mail, URL
Preconditions
You must have the following access rights to be able to enter or change machine-specific
information.
Procedure
See also
1. Documenting startup (Page 380)
2. Defining start-up (Page 380)
Making a logbook entry (Page 381)
As an alternative, you can use the "PridaNet identSNAPSHOT" program to export the machine
and address information from the EUNA database to create a selection file. This ensures that
the information is clear.
Templates
Templates for selection files are available under the directory
/HMI-data/templates/examples/machine identity.
You can find the following templates and selection files on the controller:
● "dealer.xml" for dealer data
● "ma_types.xml" for machine types
● "oem.xml" for manufacturer data
● "oemsubs.xml" for manufacturer data of a regional office
● "user.xml" for end user data
Procedure
<Customer-Id></Customer-Id>
<Name></Name>
<Street></Street>
<ZIP code></ZIP code>
<Location></Location>
<Country></Country>
<State></State>
<Contact></Contact>
<Phone></Phone>
<Fax></Fax>
<E-mail></E-mail>
<URL></URL>
</Dealer>
</Addresses>
You can list the address data of any number of manufacturers in the "oem.xml" file. If you wish
to enter additional manufacturers (OEMS), for each dealer, copy the area <Manufacturer> to
</Manufacturer>.
You can list the address data of any number of OEM regional offices in the "oemsubs.xml" file.
If you wish to enter additional regional offices, copy the area <Manufacturer-Subsidiary> to </
Manufacturer-Subsidiary>.
You can list the address data of any number of users in the "user.xml" file. If you wish to enter
additional users, copy the area <User> to </User>.
Selection files
You can import the data with any name. The data content is evaluated, and the new file name
is derived from this information:
File Information
ma_types.xml Machine types
dealer.xml Dealer's data
oem.xml Manufacturer's data
oemsubs.xml Manufacturer's data of a regional office
user.xml End customer data
Procedure
See also
Creating a selection file (Page 372)
Procedure
The "Save Version Information: Name" window opens. The following op‐
tions are available:
● In the "Name:" text field, the file name is pre-assigned with <Machine
name/no.>+<CF-card number>. "_config.xml" or "_version.txt" is
automatically attached to the file names.
● In text field "Comment", you can add a comment that is stored with
the configuration data.
Select the following data via a checkbox:
● Version data (.TXT): Output of pure version data in text format.
● Configuration data (.XML): Output of configuration data in XML format.
The configuration file contains the data you entered under Machine
identity, the license requirements, the version information and the
logbook entries.
7. Press the "OK" softkey to start the data transfer.
Precondition
You require access level 2 (service) to add more hardware components.
Category
NCU/PLC
Operator Panel
PLC-peripheral devices
Drive/Motor
Cable
Accessories/Miscellaneous
You record the following data in the "Enter Additional Components (Configuration Data)"
window.
Entries Meaning
Name Hardware designation
Version Version of the program
Order No.[MLFB] Order number
Serial number Serial number
Number Number of components
Procedure
Configuration data
The configuration data includes:
● Machine-specific data that is stored in the "Machine identity" dialog box
● Hardware/software versions that are stored in the "Versions" dialog box
● Options requiring licenses, which are stored in the "Licensing" dialog box
● Logbook, whose entries are stored in the "Logbook" dialog box
Storage path
Depending on how the drives have been configured, the configuration data can be stored in
the available directories.
See also
Machine identity (Page 370)
Adding hardware components (Page 377)
Licensing (Page 43)
Logbook (Page 379)
17.6 Logbook
The logbook provides an electronic machine history.
The time and date of commissioning is recorded in the logbook, and if the machine is serviced,
this can also be logged electronically. This helps to optimize the service.
Stored entries cannot be changed or deleted.
Precondition
As a minimum, the machine name/No., the customer No. and the country where the
manufacturer is located must be entered into the machine identity.
Procedure
Note
2. Perform commissioning
On completion of first commissioning, you will be prompted to perform the 2nd commissioning.
If the 2nd commissioning is not performed, then you will be prompted at regular intervals to
complete the 2nd commissioning.
See also
Entering machine-specific information (Page 371)
Precondition
As a minimum, the country of the end customer must be entered into the machine identity.
Procedure
Note
Registering the machine identity in EUNA
After completion of the 2nd commissioning, you are prompted to send the machine identity to
the EUNA database via the Internet.
See also
Entering machine-specific information (Page 371)
Note
If you wish to make line breaks in the "fault diagnostics/measure" field, use the key combination
<ALT> + <INPUT>.
Procedure
Note
Deleting logbook entries
Up to the end of the 2nd commissioning, you have the option to delete the logbook entries up
to the time of the first commissioning using the "Clean up" softkey.
Press the "Go to Beginning" softkey to start the search at the latest entry.
Press the "Go to End" softkey to start the search at the oldest entry.
Window switchover The form and dialog names (assigned by the programmer) are log‐
ged each time a window is opened or closed.
Writing NCK/PLC data The writing of NCK and PLC variables is logged.
File access Copying to the NC is logged.
Function calls in the NCK Some program calls, for example, ASUB, are logged.
(PI service)
Curr. program status Additional information for particular events is activated. For impor‐
tant alarms that require NC stop, NC start, or NC reset, actual val‐
ues and the current block are recorded for example.
The program ascertains which channel and which spindle are used
for the additional information.
Write interval file Settings for updating files:
● "automatic": The action log saves the information to an internal
buffer. If the buffer is full the entries are written to the CF card.
The entries may be lost when the controller is switched off.
● "after every event": All entries are backed up directly, this
prevents data loss due to a power failure or similar.
Notice: As CF cards only permit a limited number of write
accesses, this setting is not recommended for normal operation.
● "time-controlled": New entries are backed-up for a particular
length of time. An additional input field appears in which you can
specify a time in seconds.
Save log as file for alarm(s)The alarm numbers for which a "crash log" is generated are speci‐
fied. The alarms are entered separated by a comma.
Procedure
See also
Displaying the log file (Page 384)
Log files
The actual data can be displayed using the following files:
● "actual_actionlog.com"
● "actual_crashlog.com"
Procedure
3. Select the desired com file and press the "Open" softkey or double-click
the file.
4. Press the "Display new" softkey to update the display of events in the log
(actual_actionlog.com).
The entries made since the log file was called up are displayed.
Precondition
The relevant log file is open.
Procedure
- OR -
Press the "Cancel" softkey when you want to cancel the search.
1. Press the "Go to End" softkey to scroll to the end of a large log. You get
to the oldest entry of the recording.
2. Press the "Go to Beginning" software to return quickly to the most recent
log entry.
Requirement
The relevant log file is open.
Procedure
Note
The "Save log" softkey is only available for files that have not yet been saved.
Entry Description
HMI and NC version output
System:
HMI Keystrokes, window change
NC Write variables, PI services
MSG Alarm entries
USR Entries generated by the machine manufacturer for the user
ERR Action log error, e.g. log file not found
Entry keyword:
HMI_START Entry of an HMI boot
HMI_EXIT Entry of an HMI shutdown
Entry Description
PLC_CRASH Entry of a PLC crash
KEY_PRESSED Entry of a keystroke
KEY_HOLD Entry of a key hold
KEY_RELEASED Entry of a key released
ALARM_ON Entry of an incoming alarm event See below
ALARM_OFF Entry of an alarm going event "Alarm display"
ALARM_ACK Entry of an alarm acknowledgement event
OPEN_WINDOW Entry of a window opening
CHN_STATE_CHANGED Entry of a channel status change
OPMODE_CHANGED Entry of an operating mode change
TOOL_CHANGED Entry of a tool change
OVERRIDE_CHANGED Entry of override changes
DOM_CMD Entry of a download to the NC
PI_CMD Entry of a PI service
WRITE_VAR Entry of a write to NCK/PLC variable
AREA_CHANGED Entry of an area changeover
NC_CONNECTION Entry of an coming/going NC connection
USER User entry via the OEM interface
ACTIVATED Action log was activated
DEACTIVATED Action log was deactivated
INTERNAL Internal action log entry
Date/time Date and time of the event
For HMI_Start, PLC_Crash or date change since the last entry,
the intermediate period between the entry keyword and date is
designated with an "-".
Entry text Event data is written in plain text.
DETAILS If additional information regarding an entry is known, e.g. a re‐
corded IPO trace.
Example
Note
DB19.DBW24 interface signal
The DB19.DBW24 interface signal used in the example does not apply to the SINUMERIK
840D sl. It is DB1900.DBW4 for the SINUMERIK 828D.
Alarm display
MSG ALARM Date/time
No. Deletion criterion Text
DETAILS
Entry Description
MSG
ALARM Type of alarm: ALARM_ON, ALARM_OFF, ALARM_ACK
Date/time Data and time of the event
No. Alarm number
Deletion criterion: Information as to how the alarm was acknowledged
AUTOMATIC Automatic acknowledgement
POWER ON Acknowledgement using PowerOn
RESET Acknowledgement using NCK reset
NC START Acknowledgement using NC start
NC RESET Acknowledgement using NC reset
ALARM CANCEL Acknowledgement using Alarm Cancel key
RECALL Acknowledgement using the Recall key
HMI Acknowledgement using HMI
PLC Acknowledgement using PLC
Text Display of the English alarm text
DETAILS If additional information regarding an entry is known.
Example
MSG ALARM_ON 20.02.2009 14:25:37
8020 POWER ON : Option 'activation of more than 1 channels' not
set
DETAILS:
Mode: JOG Program: canceled Channel: interrupted
Program-Level information:
Level Program running: Invoc Offset
1 /_N_MPF0 0 0
Procedure
1. You can copy a sample configuration file "actlog.ini" from the following directory: /siemens/
sinumerik/hmi/template/cfg.
2. Save or create the file in the /oem/sinumerik/hmi/cfg or
/user/sinumerik/hmi/cfg directory.
3. Open the file and after "; ActionLogSize=", enter the file size (in bytes).
4. Start the trace by activating the checkbox or from any place on the user interface with the
following key combination:
<Alt> + <T> on the operator panel
<Alt> + <Shift> + <T> on an external keyboard
The following icon is displayed at the top right in the header to show that a trace is active:
5. On the user interface, repeat the operating sequence whose cause is to be clarified.
6. Stop the trace by deactivating the checkbox or from any place on the user interface with
the following key combination:
<Ctrl> + <T> on the operator panel
<Ctrl> + <Shift> + <T> on an external keyboard
7. A sltrc.out output file is generated which you can copy to the storage medium with the
"Export data" softkey.
8. Send the sltrc.out file for analysis back to the Service & Support Center.
Note
On completion of the analysis, it is recommended to delete all files under the following path: ../
user/sinumerik/hmi/log/sltrc
Note
"Extended" softkey
The other options in this dialog support suitably qualified service engineers in the analysis of
the system and evaluation of the HMI trace.
PROFIBUS connections
● DP1 X126
● DP2 X136
● DP integrated
Display Meaning/information
Status
Bus status POWER_ON (0): State after the control has been switched on
OFFLINE (1): Basic initialization has been performed
STOP (2): Start in accordance with the hardware configuration (SDB)
CLEAR (3): PROFIBUS slaves have been parameterized and configured
in accordance with the hardware configuration (SDB) and taken into the
cyclic data exchange with zero output data
OPERATE (4): Cyclic data exchange with the PROFIBUS slaves running
ERROR (9): A fatal error had been detected (e.g. invalid or faulty SDB)
(<n>) corresponds to the OPI variable value for the bus state.
Bus configuration
S7 Subnet ID S7 Subnet ID of the PROFIBUS subnet
Baud rate Transmission rate in Mbd
Cycle time Configured bus cycle time in msec; also defines the position controller
cycle at the same time
Sync. Component (TDX) Configured time interval in msec for the cyclic data exchange within a
PROFIBUS DP cycle
PROFIBUS diagnostics/slaves
Slave address Configured number of the DP slave
Assignment Information whether the DP slave is assigned to the NC or to the PLC.
NC: e.g. one or more drives controlled by the NC
PLC: e.g. I/O peripherals or an axis controlled by the PLC
NC/PLC (for DP integrated)
Communication state Information whether the DP slave is identified on the bus via the commu‐
nication state.
Green: DP slave has been detected on the PROFIBUS DP and the data
exchange is working error-free with the assigned component (NC and/or
PLC)
Red: Incorrect response / no communication
Synchr. with NC Information whether the DP slave is running synchronously to NC on the
bus.
Green: DP slave runs synchronously to NC on the PROFIBUS DP, i.e.
there is an isochronous data exchange
Red: Incorrect response / no communication
Gray: DP slave is not assigned to the NC, but to the PLC
Number of slots Number of configured slots within the DP slave
References
Further information about the configuration of the properties of the network interface for
PROFIBUS can be found in the following:
CNC Commissioning Manual: NCK, PLC, Drives, SINUMERIK 840D sl, SINAMICS S120
Procedure
2. Press the "Menu forward" key and the "Bus TCP/IP" softkey.
The "PROFIBUS Diagnostics" window is opened.
- OR -
Press the "Select bus" softkey and in the list that is displayed, select the
required configuration.
Press the "OK" softkey.
Display Meaning/information
Slave
Address The DP slave selected in the PROFIBUS diagnostics / slaves pane
Communication state Data regarding the NC and/or PLC assignment of the DP slave
In synchronism with NC Data regarding NC synchronous operation of the DP slave
If a synchronous value is not available for the DP slave, then the display
remains hidden.
Slots
No. Slot number within the DP slave
I/O addr. I/O address in the I/O address space of the PLC, assigned to this slot
For NC axes, the setpoint and the actual value must always be configured
on the same I/O address.
Type Data as to whether the slot is input, output or diagnostic slot
If the slot is assigned to an NC axis, then the output is always denoted as
setpoint value and the input always as actual value.
Length (bytes) Length of the I/O area reserved for the slot in the STEP7 I/O address space
Display Meaning/information
Communication state Actual communication state of the slot
If a value is not available for the NC axes, then the display remains hidden.
Green: Slot used by the NC, communication active
Red: Slot used by the NC, communication currently not active
Gray: No NC axis
Machine axis Display of the name defined in the machine data for this slot
If the slot is not assigned to any NC axis, then the display remains hidden.
Telegr. type (NC) Displays the assigned telegram type
If a telegram type is not assigned in the NC machine data, then the display
remains hidden.
Procedure
2. Press the "Menu forward" key and the "Bus TCP/IP" softkey.
The "PROFIBUS Diagnostics" window is opened.
3. Select the PROFIBUS configuration for which you want to display details.
4. Press the "Details" softkey.
The "PROFIBUS Diagnostics ... - Details" window is opened.
Status display
The "Drive System Diagnostics" window displays the status information about the drive units
and the associated drive objects. The status symbols have the following meaning:
Procedure
2. Press the menu forward key and the "Drive system" softkey.
- OR -
Press the "Select drive unit" softkey.
The "Select Drive Unit" window opens.
4. Select the desired drive unit via the drop-down list box and press "OK" to
confirm the selection.
See also
Displaying details of the drive objects (Page 394)
Yellow The relevant value of the drive object signals a less serious problem,
i.e. a warning is pending, for example, or enables are missing.
Red The relevant value of the drive object signals a a serious problem,
for example, an alarm is pending.
Gray The drive status could not be determined for this drive object.
Procedure
2. Press the menu forward key and the "Drive system" softkey.
3. Select the drive object for which you want to display further details.
4. Press the "Details" softkey.
The "Drive System Diagnostics - Details " window opens.
The name of the drive object is displayed in the window header.
Press the "Faults" softkey.
The "Drive Unit Faults" window opens that shows an overview of the faults
that have been output.
Press the "Alarms" softkey.
The "Drive Unit Alarms" window opens that shows an overview of the
alarms that have been output.
You can display the pending SI messages if Safety Integrated is integra‐
ted in your controller.
● Variable PingTransmissionInterval
Duration in seconds after which send is repeated,
e.g. PingTransmissionInterval = 15
● Variable PingServerPor
Port number of the Ping service with the manufacturer,
e.g. PingServerPort=6201
1&8
;
76DGDSWHU 6HUYLFH3&
Figure 17-1 Basic system with SINUMERIK Operate on NCU (and operating station with TCU)
With the previously mentioned settings and the default values, in this configuration, remote
diagnostics via TS Adapter is possible without any additional changes having to be made.
6,180(5,.2SHUDWH
RQVW3&8
;
;
1&8
;
7HOHVHUYLFHDGDSWHU 6HUYLFH3&
With the previously mentioned settings and the default values, in this configuration, remote
diagnostics via TS Adapter is possible without any additional changes having to be made.
When operating a SINUMERIK Operate on a PCU, the SINUMERIK Operate in the NCU must
be switched off.
;
76DGDSWHU 6HUYLFH3&
The "MC Information System RCS Host" option only has to be set for the NCU to which the
TS Adapter is connected at the X127 interface. Modem access can only be permitted by making
the appropriate entries at the SINUMERIK Operate in this NCU and the "Request remote
control" function executed. If modem access is permitted, then the service PC implicitly has
access to all other NCUs and their operating software. On the other hand, the operating
screens to control the remote access can be used and set at each station
(SINUMERIK Operate in the NCU) individually for the station in conjunction with the relevant
local PLC.
6,180(5,.2SHUDWH
6,180(5,.2SHUDWH
6,180(5,.2SHUDWH
RQVW3&8 RQQG3&8 RQUG3&8
;
7HOHVHUYLFHDGDSWHU 6HUYLFH3&
Figure 17-4 System with several NCUs, several PCUs and a fixed modem
The "MC Information System RCS Host" option only has to be set for the NCU to which the
TS Adapter is connected at the X127 interface. Modem access can only be permitted by making
the appropriate entries at the SINUMERIK Operate on the PCU that is assigned to this NCU
and the "Request remote control" function executed. If modem access is permitted, then the
service PC implicitly has access via the plant or system network to all other NCUs and PCUs
and their operating software. The operating screens to control the remote access can be
individually used and set at each station (SINUMERIK Operate in the NCU) for the station in
conjunction with the relevant local PLC.
DB19.DBX1.0 PLCExtViewerReject
Value =0 =1
Meaning Permit remote control No remote control
DB19.DBX1.1 PLCExtViewerMode
Value =0 =1 ignored
17.12 Trace
The trace provides you with an oscilloscope function that allows the following data (signals) to
be graphically displayed:
● General NC data
● PLC data
Trace session
The function serves for troubleshooting and resolving faults as well as to analyze the machine
and process performance. In a session, data (signals) are recorded briefly before and after an
event.
Graphic display
The recorded data is optically displayed in the form of curves, the so-called characteristics
graphs.
You have the option of individually setting the recording type.
Cyclic events
Interpolation clock cycle (IPO clock cycle)
PLC cycle OB1
Position control clock cycle (servo clock cycle)
Non-cyclic events
Starting a session
● Recording using a trigger
● Manually starting and stopping a trace
See also
Variable for trace (Page 405)
Trace settings (Page 411)
Trace options (Page 413)
Saving the trace file (Page 403)
Evaluate a trace (Page 414)
Procedure
See also
Variables filter/search (Page 405)
Procedure
- OR -
If the session file with this name already exists, then you obtain a corre‐
sponding confirmation prompt.
Settings Meaning
Variables, settings You can restart a trace session that has already been created.
Variables, settings and recorded val‐ You can view the result of a trace session, change the variable
ues and if required, restart.
Precondition
A session file of recorded traces is available.
Procedure
- OR -
Select the checkbox "Variables, settings and recorded values", if you wish
to display the trace session.
Press the "OK" softkey.
The data of the selected session are loaded displayed in the "Trace"
window.
Inserting variables
The start value for the "Filter/Search" of variables differs. For example, to insert the variable
$R[0], enter the following start value:
● The start value is 0 if you filter according to "System variables".
● The start value is 1 if you filter according to "All (no filter)". In this case, all signals are
displayed and shown in the OPI notation.
The GUD from the machine data is only displayed in the Search window for the variable
selection when the associated definition file has been activated. Otherwise, the sought
variables must be entered manually, e.g. GUD/SYG_RM[1]
The following machine data is representative for all variable types (INT, BOOL, AXIS, CHAR,
STRING): MD18660 $MN_MM_NUM_SYNACT_GUD_REAL
Procedure
For a trace session, in the "Selected Variables for Trace: Session ... " window, set the variables
whose signals are to be traced.
5. Press the "Add" softkey to enter the required variable into a trace session.
The "Variable Attributes" window opens and you can select the appropri‐
ate value (e.g. channel data, drive bus no.) from a combobox.
- OR -
Press the "Replace" softkey to replace an already selected version by
another one.
6. Press the "OK" softkey to add or replace the variable.
Each variable is automatically allocated a reference number, which is
displayed in the upper section of the window. This number is opened
automatically allocated. If a version is removed, then the following varia‐
bles are re-numbered.
7. Now, select the desired settings for display, such as color, pen, qty.,
event. etc.
Attributes
For a trace session, select the variables and assign the corresponding attributes:
Column Meaning
Variable Address of the variables
Attributes Meaning
Comment ● Name of the selected variables
● A general description for the variables.
Color Color selection, the representation of the characteristic graphs.
When creating a variable, the next color from the available palette is automati‐
cally used.
Attributes Meaning
Pen Line type selection to display the characteristic graphs.
● No line
● Solid line
● Dashed line
● Dash-dot line
● Dash-dot-dot line
● Dotted line
● Stepped line XY
● Stepped line YX
● "* line" (line made up of * symbols)
● + line
● X line
Qty. Defines whether the characteristic of the variables is displayed in the "Trace"
window. If the checkbox is not selected, then no characteristic graphs are dis‐
played.
Events Event selection which triggers that the signal is traced:
● Interpolation clock cycle (IPO clock cycle)
● Interpolation cycle (IPO2)
● Position control clock cycle (servo clock cycle)
● PLC cycle OB1
● Drive trace rate
● Start geometry axis/direction change
● Stop geometry axis
● Machine axis start / direction change
● Machine axis stop
● NC start (program runs)
● NC start (program ran)
● Start of the data recording
Attributes Meaning
● Block start, type 1 or block end (all program levels, without intermediate
blocks)
● Block start, type 2 or block end (all program levels, with intermediate blocks)
● Block start, type 3 or block end (all main programs, without intermediate
blocks)
● Block start or block end, block search (all program levels, without
intermediate blocks)
● Geo axis start / direction change (2nd event)
● Geo axis stop (2nd event)
● Block start, type 2 (2nd event: all program levels, without intermediate
blocks)
● Block end, type 2 (2nd event: all program levels, with intermediate blocks)
● Block start, block advance, type 1 (2nd event)
● OEM test event 1 (non-cyclic, block advance)
● OEM test event 2 (non-cyclic, main run)
● Activate/deactivate synchronized action
● Synchronized action initiated (condition fulfilled)
● Signaled alarm
● Cancel softkey pressed
● Program level change
● Block end (Interpreter)
● Trace end (last event!)
● Start trace
● WRTPR part program command
● WRTPR part program command (block search)
● Tool change
● Cutting edge change
● Tool change (block search)
● Cutting edge (block search)
● Start trigger initiated
● Stop trigger initiated
● Block end (block advance)
● Block end (2nd event: Block search)
● WRTPR part program command (block advance)
● Tool change (block advance)
● Cutting edge (block advance)
Event channel This means that the channel can be defined in SINUMERIK in which a specific
event occurs. For events which are not channel-specific, the field remains emp‐
ty.
Attributes Meaning
Bit mask In the case of an integer variable, a bit mask can be specified in this field. For
a bit mask, the particular signal value is AND'ed before being displayed. After
the mask has been applied, all of the selected bits are moved to the right so
that it looks as if the bit or the bits all start with bit zero.
This means, if all bits with the exception of bit 7 have been masked, then the
integer number that would have been obtained would either have a value of 0
or 1, however, not 0 or 128.
If all of the bits with the exception of bit 7 and 0 have been masked, the resulting
integer number would either have the value 0, 1, 2 or 3, however, not 0, 1, 128
or 129.
Decimal places This setting is used to define how many places to the right of the decimal point
are displayed at the axis identifiers.
Coord. axis The coordinate axes are displayed to the left or right in the graphic window or
there is no display.
Display Y Value input or 0
Scale factor Defines the scale.
Units Displays the measurement unit, e.g. mm/min. The system specifies this and it
cannot be changed.
Variable: Details
The most important information and settings are displayed at a glance in the detail window:
● Variable address
● Comment with a description of the variables
● Events
● Channel, axis, access level, mode group, etc.
● Smaller graphic display with the event; when this event occurs the characteristic graphs
are recorded as well as their attributes, such as color or line type.
Procedure:
Procedure
1. You are in the "Select Variables for Trace: ..." window and a trace ses‐
sion has been selected.
2. Press the "Options" softkey.
The "Trace - Options" window opens.
3. Select the desired settings and press the "OK" softkey in order to accept
the settings.
Procedure
- OR -
The recording is triggered by the trigger condition.
4. If you wish to manually end the recording, press the "Stop trace" softkey.
- OR -
The recording is stopped by the trigger condition.
Requirement
The "Trace" graphic window is open and the trace has been recorded.
Editing curves
You jump from one variable to the next using the <TAB> key.
With the cursor keys, you set marks, move to individual values and can
define a zoom range.
Legend
Numbering the variables
Axis identifier
Comment of the variables
Setting Meaning
X minimum or Highest or lowest value of the X time axis. The values are used for recording
X maximum when the trace is started again.
Fixed scale, X axis Values of the X time axis are kept.
Strip chart recorder mode The values of the X time axis are used while
recording.
Y minimum or Defining the highest or lowest value of the Y value axis (amplitude).
Y maximum
Offset or Defining the rms values (mean values) of the amplitudes.
resolution The scale is changed by a factor of 10.
The "Select X-Y Scaling" input window opens and the values of the X time
axis are displayed.
3. Press the "X time axis" softkey again if you wish to hide the values.
- OR -
Press the "Y selected curves" softkey to display the values of the Y value
axis.
Press the softkey again if you wish to hide the values.
- OR -
You have selected both axes.
4. Press the "Scale +" or "Scale -" softkey until the desired scaling is reached.
- OR -
Enter the scaling values directly into the input window and select the ap‐
propriate property.
5. Press the "Scale" softkey to save the settings.
- OR -
Procedure
2. Press the "Zoom" softkey if you wish to zoom-in or zoom-out on the char‐
acteristic graphs.
3. The "X time axis" or "Y value axis" softkey is selected.
4. Press the "Adapt individually" or "Adapt all" softkey if you wish to display
all selected characteristic graphs in a separate area positioned one above
the other.
or
- OR -
Press the "Adapt together" softkey if you wish to adapt all of the charac‐
teristic graphs to the graphic window.
As all of the curves fill the complete window area, they are displayed
superimposed on one another.
- OR -
Press the "Individually adapt X" softkey if you wish to normalize the X time
axis only in the graphic window.
- OR -
Press the "Individually adapt Y" or "Adapt all" softkey if you only wish to
scale the Y value axis in the graphic window.
or
- OR -
Press the "Adapt Y together" softkey if you wish to adapt the value axis
of all characteristic graphs to the graphic window.
As all curves fill the complete window area, they are displayed superim‐
posed.
5. Press the "Zoom +" or "Zoom -" softkey until the desired display size is
reached.
Procedure
5. Press the "Both cursors" softkey to display the area between A and B.
The coordinates of A and B as well as the difference "Δ" are displayed in
the status line.
Press the active "Cursor A" and "Cursor B" softkeys again to deselect the
position.
When re-selected, the positions are reset.
Press the "Crop to screen" softkey to display the area, defined by "Cursor
A" and "Cursor B", in the complete graphic window.
Press the "Snap to waveform" softkey to move the cursor along the curve
step-by-step.
Procedure
Press the "Point Mode" softkey to continuously move the cursor along the
curve.
Press the "Peak Mode" softkey to position the cursor at the highest value.
Press the "Valley Mode" softkey to position the cursor at the lowest value.
If you press the "Peaks" softkey, the cursor only goes to the peak-peak
values.
If you press the "Minimum" softkey, the cursor only goes to the peak-valley
values.
17.13.1 PROFIBUS/PROFINET
With the PROFIBUS/PROFINET diagnostics, you obtain a quick overview from which, when
required, you can call status and detailed information for external DP master systems and
PROFINET IO systems.
Software option
For faulted modules, in order that in addition to the status information, detailed
information can also be displayed, you now require the following option:
"Operating software SW HMI PRO sl RT".
In order that detailed information can be displayed for PROFINET-IO systems, the PLC block
FB_SL_COM from the HMI PRO block library must be used. Use DB449 as the associated
instance DB.
Note
Detailed information for DP master systems is also available without using FB_SL_COM.
The following diagnostics information is displayed depending on the particular version that you
have configured:
Module is OK
Procedure
2. Press the "Menu forward" key twice and the "PB/PN diag." softkey.
The "PROFIBUS/PROFINET Diagnostics" window opens.
Precondition
● For AS-i diagnostics, it is absolutely necessary to use the FB_SL_COM PLC block from the
HMI PRO block library.
● The configuration file "sltlprodiaghmi.ini" must be available.
AS-i components
The following AS-i components are supported:
CP142-2 (Type ID 1)
CP343-2 (Type ID 2)
DP/AS-i link (Type ID 3)
DP/AS-i link 20E (Type ID 4)
DP-AS-i link Advanced (Type ID 6)
Diagnostic information
All of the AS-i components to be diagnosed must be parameterized in the "sltlprodiaghmi.ini"
configuration file.
Entry Description
[SKO]
ComboCount=x Number of entries (x) in the selection list
[SKO_Index0] 1. Entry
DiagType= 6 Type ID of the AS-i component (refer above)
TypeSection=DP-AS-i-Link- Designation of the AS-i component, which should be
Advanced 1 output in the selection list
Entry Description
Logical_Address=43 E address of the AS-i component from the hardware
configuration
RequestDB=449 Instance DB of the function block "FB_SL_COM" be‐
ing used
[SK0_Index0]
DiagType= 1
TypeSection=CP142-2
Logical_Address=43
RequestDB=449
[SK0_Index1]
DiagType= 2
TypeSection=CP343-2
Logical_Address=75
RequestDB=449
[SK0_Index2]
DiagType= 3
TypeSection=DP-AS-i-Link
Logical_Address=75
RequestDB=449
[SK0_Index3]
DiagType= 4
TypeSection=DP-AS-i-Link-20E
Logical_Address=75
RequestDB=449
[SK0_Index4]
DiagType= 6
TypeSection=DP-AS-i-Link-Advanced
Logical_Address=75
RequestDB=449
Procedure
1. Copy the "sltlprodiaghmi.ini" file from the /siemens/sinumerik/hmi/template/cfg directory.
2. Place the file in the directory: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg.
If the file is already available in the directory, then just supplement this by the corresponding
entries.
3. Open the file and enter the corresponding data of the AS-i components.
4. Save and close the file.
The diagnostics information is displayed on the user interface.
Software option
Additional error counter can be displayed for the component DP-AS-i Link Ad‐
vanced if the option "Operating SW HMI PRO sl RT" is set.
Diagnostic information
State Marking
Slave OK Green
Slave fault Red
Slave is available, but not configured Yellow
Procedure
2. Press the menu forward key twice and the "AS-i diag." softkey.
The "Diagnostics AS-Interface" window is opened.
Procedure
1. Generating HTML files
2. Generating a help book
3. Integrating the online help in SINUMERIK Operate
4. Saving help files
Note
The "SINUMERIK HMI programming package sl" must be ordered separately as a software
option. The associated documentation is provided together with the programming package.
HTML tags
Block attributes
The following attributes are supported by the tags div, dl, dt, h1, h2, h3, h4, h5, h6, p:
● align (left, right, center, justify)
● dir (ltr, rtl)
CSS properties
The following table includes the supported CSS functional scope:
The book comprises three sections, whereby the third section has two subsections. The
various subject words (keywords) are defined within the section.
You have the following three options to format the subject index:
1. Single entry:
<INDEX_ENTRY ...title="index"/>
2. Two two-stage entry, whereby each title has a main and a subentry. Separate the entries
from one another using a comma.
<INDEX_ENTRY ...title="mainIndex_1,subIndex_1 with mainIndex_1"/>
3. Two-stage entry, whereby the first title is the main entry and the second title is the subentry.
Separate the entries from one another using a semicolon.
<INDEX_ENTRY ...title="mainIndex_2;subIndex_2 without
mainIndex_1"/>
See also
Supported languages (Page 612)
18.6 Generating online help for user alarms and machine data
You have the option to create a dedicated online help for user-specific PLC alarms. These can
be opened context-sensitive from the alarm list when the alarms occur.
The help texts for the user-specific PLC alarms are realized in the HTML file
"sinumerik_alarm_oem_plc_pmc.html".
3. Place the files in the corresponding language directories. For instance, place the file for the
German help text in the following directory: /oem/sinumerik/hmi/hlp/deu/
sinumerik_alarm_plc_pmc/sinumerik_alarm_oem_plc_pmc.html
4. Delete the file "slhlp_sinumerik_alarm_plc_pmc_*.hmi" in the /siemens/sinumerik/
sys_cache/hmi//hlp directory and restart the operating software.
"sinumerik_alarm_oem_plc_pmc.html" file
Entry Meaning
<a name="AlarmNr">AlarmNr</a> Hyperlink to the alarm number
<b> .....</b> Help text for the corresponding alarm
<td width="85%">......</td> Text that is displayed after the "Explanation" or "Remedy" field.
Example
The alarm number is used as HTML anchor.
</body>
</html>
Distribute the online help for user alarms over several HTML files
You have the option of distributing the online help for user alarms over several HTML files.
1. Create an XML file with the name "sinumerik_alarm_plc_pmc.xml" in the following
directory: /oem/sinumerik/hmi/hlp/<lng>/ or /user/sinumerik/hmi/hlp/<lng>/
<lng> stands for the language code, e.g. deu, eng, etc. When you create a language
directory, use the language code from the table in Section Supported languages
(Page 612)
2. Open the XML file and in the tag <NUM_AREAS> enter the number ranges of the alarms
and the corresponding HTML files.
3. Store the HTML files, specified in the XML file, in the following directory:
/oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_plc_pmc or
/user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_plc_pmc file
Entry Meaning
<BOOK> Help book
<NUM_AREAS> Number ranges of the alarms and the reference to the particular HTML file
Area Directory
PLC alarms /oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_plc_pmc/ or
/user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_plc_pmc/
HMI alarms /oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_hmi/ or
/user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_hmi/
NC alarms /oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_nck/ or
/user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_nck/
NC MD /oem/sinumerik/hmi/hlp/<lng>/sinumerik_md_nck/
Channel MD /oem/sinumerik/hmi/hlp/<lng>/sinumerik_md_chan/
Axis MD /oem/sinumerik/hmi/hlp/<lng>/sinumerik_md_axis/
<lng> stands for the language code, e.g. deu, eng, etc. Only use the language codes from the
table in SectionSupported languages (Page 612)
Procedure:
1. Create the corresponding directory, refer to the table "Directory for HTML files".
2. Generate the help file and as file names, use the alarm/machine data number as well as
the extension ".html" for HTML help files and ".pdf" for PDF help files. If you create help
texts for several languages, then create the corresponding number of help files with
precisely these names and then create the file in the corresponding language directory.
Examples:
● Your own German online help for the PLC Alarm 510000:
/oem/sinumerik/hmi/hlp/deu/sinumerik_alarm_plc_pmc/510000.html
/oem/sinumerik/hmi/hlp/deu/sinumerik_alarm_plc_pmc/510000.pdf
● Your own German online help for the NC machine data 14510 $MN_USER_DATA_INT:
/oem/sinumerik/hmi/hlp/deu/sinumerik_md_nck/14510.html
18.7 Example: This is how you create an online help for NC/PLC variables
Overview
In order to create context-sensitive online help for NC/PLC variables or system variables as
shown in the following example, the descriptive texts are managed in language-dependent
html files.
File Meaning
sldgvarviewhelp.ini Configuration file to manage an html file or several html
files
<lng>/<name>1.html The contents of all html files of the online help are lan‐
<lng>/<name>2.html guage-dependent and are saved in the relevant language
directory <lng>.
. . .
<lng>/<name>n.html
sldgvarviewhelp.ini
[HelpBindings]
sldgvarviewhelp.ini
/BAG/STATE/OPMODE = var1_help.html#var1
$AA_IM[X1] = var1_help.html
$R[1] = var1_help.html#var2
/Channel/Parameter/R[u1,1] = var2_help.html#var2
DB2.DBX180.0 = var2_help.html#var1
GUD/MyVar[2] = var2_help.html
Note
The html files can be generated with any html editor. A definition is provided in the configuration
file as to which html files belong to the online help.
The description can comprise one or several html files: For example, one html file for each
variable or several identical variables in one file.
Procedure:
1. Copy the configuration file to the following directory:
/oem/sinumerik/hmi/cfg/sldgvarviewhelp.ini
2. Copy the html files to one of the following directories:
/oem/sinumerik/hmi/hlp/<lng>/
/user/sinumerik/hmi/hlp/<lng>/
<lng> stands for the language code.
Preconditions
Create the following files:
● Configuration file "prog_help.ini"
[milling]
CYCLE1=cycle1_help.html
CYCLE2=cycle2_help.html#TextAnchor1
CYCLE3=cycle3_help.html
CYCLE4=cycle4_help.html
[turning]
CYCLE3=cycle2_help.html
CYCLE4=cycle3_help.html
3. Create a directory for the desired language of the online help under the following path: /
oem/sinumerik/hmi/hlp/<lng> and copy the hmi_prog_help.xml file there
Use the specified language code from the list of language codes for file names. The
directory names must be written in lower case.
4. Copy the language-dependent prog_help_<lng>.ts file for the Product Brief to the
following path: /oem/sinumerik/hmi/<lng>/prog_help_<lng>.ts
5. Copy the html files with the description of the OEM cycles to the following directory:
/oem/sinumerik/him/hlp/<lng>/hmi_prog_help/cycle<n>_help.html
The settings become effective only after restarting the system.
Note
It is not possible to select context-sensitive jump labels in the PDF help, select jump labels or
make jumps to other HTML or PDF files.
The search function is possible only within a PDF file. A higher-level search over multiple PDF
helps is not supported.
Configuring a softkey
MD9108 $MM_SINUMERIK_INTEGRATE
=1 The "SINUMERIK integrate" softkey is displayed on the extended user interface bar.
References
Information on the software can be found in the following documentation:
Function Manual SINUMERIK Integrate - AMB, AMC, AMM
References
Function Manual, SINUMERIK Safety Integrated
Procedure
3. Press the "All axes" softkey if you wish to display all of the axes.
The "All Axes Machine Configuration" window opens and the "All axes"
softkey changes into "Safety axes".
4. Press the "Safety axes" softkey in order to return to the view of the safety
axes.
See also
Copying and confirming Safety Integrated data (Page 451)
Activating/deactivating start-up mode (Page 452)
Displaying the Safety-Integrated settings (Page 453)
Note
Changes as well as copying and confirming are effective for all axes and the general machine
data.
Screen view
The machine data display is split into two halves:
● In the upper part of the screen view, the machine data that are important for commissioning
are displayed; however, they do not involve Safety Integrated machine data.
● Safety Integrated machine data are displayed in the lower part of the screen view.
1. Press the "MD selection" to change into the full screen view.
The selection of general machine data is displayed over the complete
screen.
2. Press the "SI-MD" softkey.
The general safety integrated machine data are displayed over the full
screen.
3. Press the "SI + MD selection" softkey.
You return to the common view split in two of the general machine data
and the Safety Integrated machine data.
1. Press the "Search" softkey, enter the machine data number being
searched for in the window that opens or a character string that is being
searched for an press the "OK" softkey.
2. Press the "Continue search" softkey if the text position found does not
correspond to the required machine data.
3. Press the "Go to start" or "Go to end" softkey to set the cursor to the
beginning or to the end of the displayed data.
4. Press the "Search" softkey if you wish to change the search term.
Screen view
The machine data display is split into two halves:
● In the upper part of the screen view, the machine data that are important for commissioning
are displayed; however, they do not involve Safety Integrated machine data.
● Safety Integrated machine data are displayed in the lower part of the screen view.
1. Press the "MD selection" to change into the full screen view.
The selection of Axis MD is displayed over the complete screen.
2. Press the "SI-MD" softkey.
The Safety Integrated Axis MD are displayed over the complete screen.
3. Press the "SI + MD selection" softkey.
You return to the common view split in two of the general machine data
and the Safety Integrated machine data.
1. Press the "Search" softkey, enter the machine data number being
searched for in the window that opens or a character string that is being
searched for an press the "OK" softkey.
2. Press the "Continue search" softkey if the text position found does not
correspond to the required machine data.
3. Press the "Go to start" or "Go to end" softkey to set the cursor to the
beginning or to the end of the displayed data.
4. Press the "Search" softkey if you wish to change the search term.
1. Press the "Search" softkey, enter the machine data number being
searched for in the window that opens or a character string that is being
searched for an press the "OK" softkey.
2. Press the "Continue search" softkey if the text position found does not
correspond to the required machine data.
3. Press the "Go to start" or "Go to end" softkey to set the cursor to the
beginning or to the end of the displayed data.
4. Press the "Search" softkey if you wish to change the search term.
Note
Certain NCK machine data is not copied into the drive parameters.
When confirming the data, the actual checksum is saved in the reference checksum.
Note
The data is saved for all safety axes.
Requirement
Procedure
2. Press the "Axis MD" softkey and select an axis using the "Axis +" or "Axis
-" softkey if you wish to copy axis-specific machine data and safety data.
Procedure
3. Press the "Drive MD" softkey and select the desired drive using the "Drive
+" or "Drive -" softkey.
- OR -
...
Press the "View axes" softkey.
You can use the softkeys to scroll between the Safety Integrated axes.
Procedure
See also
View of the axes (Page 447)
Available signals
● Safe actual position
● Position deviation NCK/drive
● "Safe operating stop" monitoring active
● "Safe velocity" monitoring active
● Active SV step
● Active SV correction factor
● Safe actual velocity limit
● Set velocity limit
● Current velocity difference
● Maximum velocity difference
● Active safe software limit switch
● Active gear ratio (step)
● Active stop
● Currently requested external stop
● Stop F code value
● Pulses enabled
● Traversing inhibit, stop in other axis
Procedure
Press the "Axis selection" softkey and select the desired axis directly from
the displayed list of available axes.
SGE
Safe input signals, NCK Bit15...0
Safe input signals, drive Bit15...0
Safe input signals, NCK, Bit 16...31
Safe input signals, drive, Bit 16...31
SGA
Safe output signals, NCK Bit15...0
Safe output signals, drive Bit15...0
Safe output signals, NCK, Bit 16...31
Safe output signals, drive, Bit 16...31
Procedure
3. Press the "SGE/SGA" softkey to display the safety-related input and out‐
put signals.
The "Safety Integrated SGE/SGA" window appears.
- OR -
Press the "Axis selection" softkey and select the desired axis directly from
the displayed list of available axes.
Variables
$A_INSE (P) $A_INSE (P) - corresponds to simultaneous selection of:
$A_INSE (upper line, origin of the NCK) and
$A_INSEP (lower line, origin of the PLC)
$A_OUTSE (P) comp. $A_INSE (P)
$A_INSI (P) comp. $A_INSE (P)
$A_OUTSI (P) comp. $A_INSE (P)
$A_MARKERSI (P) comp. $A_INSE (P)
$A_PLCSIIN comp. $A_INSE (P)
$A_PLCSIOUT comp. $A_INSE (P)
Available signals/values
DCC fill level
DCC status
DCC control word
SPL booting state
SPL started up
SPL interfaces have been parameterized
SPL program file SAFE.SPL loaded
NCK and PLC state
Interrupt for PLC start should be assigned
Interrupt has been assigned for PLC start
Interrupt processing for SPL start called
Interrupt processing for SPL start terminated
SPL start implemented using PROG_EVENT mechanism
SPL started via AUTO start
SPL processing completed, end of program reached.
Procedure
3. Press the "SPL" softkey to display the safe programmable logic signals.
The "Safety Integrated SPL" window is opened
Procedure
Press the "Axis selection" softkey and select the desired axis directly from
the displayed list of available axes.
Supported functions
The following Safety Integrated functions (Safety Integrated Basic Functions) are available:
These functions are available in the standard drive version.
● Safe Torque Off (STO)
STO is a safety function that prevents the drive from restarting unexpectedly in accordance
with EN 60204-1.
● Safe Stop 1 (SS1, time controlled)
The SS1 function is based on the “Safe Torque Off” function. This means that a Category
1 stop in accordance with EN 60204-1 can be implemented.
● Safe Brake Control (SBC)
The SBC function permits the safe control of a holding brake.
Note
Safety Integrated Basic Functions
When a drive object that has Safety Integrated functions released is switched to "Parking"
state, the Safety Integrated software responds by activating STO without generating a
separate message.
References
Function Manual, SINUMERIK Safety Integrated
Procedure
6. Press the "Drive selection" softkey and in the drop-down list that appears,
directly select the desired drive object.
Procedure
Procedure
2. Press the "Menu forward" key and then the "Safety" softkey.
- OR -
Press the "Axis selection" softkey and select the desired axis directly from
the displayed list of available axes.
Procedure
2. Press the "Menu forward" key and then the "Safety" softkey.
Displayed signals
The following signals of the selected connection are displayed:
● CPU-CPU communication ID
● Logical base address
● Connection number
● Maximum parameterized communication time
● Actual communication time
● Maximum communication time
● Error reaction
Error reactions that can be set:
– [0] "Alarm 27350 + STOP D/E"
– [1] "Alarm 27350"
– [2] "Alarm 27351 (self clearing)"
– [3] "No reaction"
● Error
● Diagnostics error code
● Substitute values active
● Actual communication data
● Driver state
Status display:
– [0] "Not initialized"
– [1] "Establish communication after booting"
– [2] "Establish communication after error"
– [3] "Wait for checkback signals SN=1"
– [4] "Receiver waits for user acknowledgement"
– [5] "Normal operation"
Procedure
Displayed signals
The following signals of the selected connection are displayed:
● CPU-CPU communication ID
● Logical base address
● Connection number
● Maximum parameterized communication time
● Actual communication time
● Maximum communication time
● Error reaction
Error reactions that can be set:
– [0] "Alarm 27350 + STOP D/E"
– [1] "Alarm 27350"
– [2] "Alarm 27351 (self clearing)"
– [3] "No reaction"
● Error
● Diagnostics error code
● Substitute values active
● Substitute values
● Actual communication data
● Driver state
Status display:
– [0] "Not initialized"
– [1] "Establish communication after booting"
– [2] "Establish communication after error"
– [3] "Wait for checkback signals SN=1"
– [4] "Receiver waits for user acknowledgement"
– [5] "Normal operation"
Procedure
4. Press the "Display SPL connection " softkey to display additional details,
e.g. connection data that has been set.
The softkey is only available if send connections have been configured.
5. Press the "Display connection" softkey to return to the window with the
receive connections of the selected connection.
Note
Cylindrical and surface grinding are not supported as a technology extension by SINUMERIK
Operate.
References: Loops
For further information about the grinding technology, please refer to:
● Chapter "grinding (Page 515)"
● Operating Manual, Grinding
● Programming Manual, Production Planning; Chapter "Programming cycles externally" >
"Technological cycles":
– CYCLE495 - form-truing
– CYCLE4071 - CYCLE4074: Longitudinal grinding cycles
– CYCLE4075 - CYCLE4079: Surface grinding cycles
● Function Manual, Extended Functions; Compensations (K3),
Section: "Interpolatory compensation" > "Cylinder error compensation"
= < =
< <
;
; ;
; = < =
= ; = ;
< <
; <
; = < =
; = ;
= =
< <
< =
; < ;
; = ;
=
< < <
< ; = = ;
< ; < =
;
= = ;
=
< ; <
< = <
; ; =
= =
< ; <
;
= <
< = ; ;
;
=
;
< = <
< = <
= ; ;
;
;
< = = <
; < ; =
< <
= =
=
; < ;
; = ;
<
< =
=
= ; < < ;
; =
= < <
;
<
;
< = ; =
; = <
= ; <
<
< ;
= ; =
Note
The specified default values are valid for the metric system and are converted by the NC
automatically on the machine with the inch setting.
Additional settings
See also
Technology cycles for swiveling (Page 517)
Drilling technology
You can set drilling technology using the following channel-specific configuration machine data
and channel-specific cycle setting data.
Tapping (CYCLE84)
CUST_832.SPF Manufacturer cycle for the adaptation of the high-speed settings function
(CYCLE832)", see Chapter Manufacturer cycle CUST_832.SPF
(Page 572)".
CUST_MEACYC.SPF Manufacturer cycle for the adaptation of the measuring functions, see
Chapter "Manufacturer and user cycle CUST_MEACYC.SPF
(Page 578)".
CUST_MEAPROT.SPF Manufacturer cycle and user cycle for the adaptation of the log form and
content, see Chapter "Manufacturer and user cycle CUST_MEAP‐
ROT.SPF (Page 606)".
PROG_EVENT.SPF Standard cycle to support the following functions:
● Block search when milling or turning is activated
● Block search and swivel plane
● Block search and align / advance tool
Observe MD52212 $MCS_FUNCTION_MASK_TECH bit 3 and bit 5.
CUST_T Cycle is used to track the T preparation after SERUPRO.
CUST_M6 Cycle is used to track the tool change after SERUPRO.
CUST_MULTICHAN Manufacturer cycle for lathes with several channels
CUST_CLAMP Manufacturer's cycle for clamping elements
Note
When upgrading the software, please refer to the upgrade instructions.
Configuration
If you use feedback signals regarding the machine state, e.g. in CYCPE1MA, for tool change
cycles, measuring cycles or CUST_800, then in the NC program you must link in the following
system variables in order to avoid PLC access. Otherwise, PLC access prevents data
alignment, results in alarms or the simulation being canceled:
Example
In the following example, the simulation mode in PROG_EVENT or CYCPE1MA.SPF is
stopped by the PLC access:
N100 REPEAT
N110 UNTIL PLC_VAR <> 0
If you use the system variable $P_SIM, then PLC access in the simulation mode is prevented:
N099 IF NOT $P_SIM
N100 REPEAT
N110 UNTIL PLC_VAR <> 0
N111 ENDIF
Procedure
Function
The two cycles are used to track the T preparation (CUST_T) and the tool change (CUST_M6)
according to SERUPRO. In so doing, depending on the specific tool holder, the following is
output:
● Last programmed change
● Last programmed preparation
Precondition
The cycles can only be used when tool management is active.
Sequence
The two cycles are called in the "SERUPRO-END-ASUB", which also provides the two transfer
parameters.
Parameter Meaning
_THnr Tool holder or master spindle number that was programmed for the change or the
preparation.
_MTHnr Number of the active tool holder or master spindle at the time of programming.
The cycles themselves do not contain and "machine logic". Pure data operations are performed.
The active tool holder or the master spindle is saved.
Using the transfer parameter, the situation at the time of the T or M6 programming is
determined. This situation is established, T and/or M06 output or a branch is made into the
manufacturer cycles. After the output of T and M06 or after returning from the manufacturer
cycles, the tool holder, saved at the beginning, is reactivated.
A change cycle can then only be called without any restriction, if the corresponding queries
such as program test, block search,...exist.
T replacement cycle
If a T replacement cycle is being used, then the following note must be observed:
Note
The CUST_T cycle uses the language command TCA (ToolChangeAbsolut) for the T call and
therefore also has the possibility of inserting tools that have been disabled. However, this
language command cannot be substituted.
The following must be observed if working at a machine with T replacement:
● The T preparation cycle must be explicitly called at the specified position.
● If the call is realized using the CUST_T cycle, then the parameter evaluation
($C_TS_PROG, …) is skipped.
Alternatively, the original TCA language command can be reprogrammed.
References
Function Manual Basic Functions; Auxiliary function outputs to PLC (H2),
Section: "Behavior during block search" > "ASUB at the end of the SERUPRO"
Function
For technological cycles, the CUST_TECHCYC cycle is called from ShopMill and ShopTurn
cycles, if the machine builder must make certain adaptations to a specific machine (e.g.
activate specific M commands). For instance, this may be necessary in order to retract or
extend part catchers when cutting off parts on lathes or to position a spindle for clamping (only
in JobShop).
The CUST_TECHCYC.SPF cycle can be used to program and execute the necessary
sequences.
Marker Action
_M1 Main spindle: Changeover to C axis mode
_M2 Changeover to spindle mode
_M3 Clamp C axis
_M4 Release C axis clamping
_M5 Rinse chuck
_M6 Close chuck
_M7 Open chuck when spindle is stationary
_M8 Open chuck when spindle is rotating
_M9 Flush chuck
_M30 4. Position axis after block search (e.g. counterspindle, tailstock, back rest)
Marker Action
_M100 Drawer: Position before cut-off
_M101 Open during cut-off
_M102 Close after cut-off
_M103 Cut-off completed
Marker Action
_M231 Start of program (ShopMill program)
_M232 End of program header (ShopMill program)
_M235 End of program loop (ShopMill program)
_M236 End of program (ShopMill program)
Function
The CUST_MULTICHAN cycle is used for multi-channel programming at lathes. It is called at
the start of the block when programming with blocks.
In the cycle, e.g. the master spindle is set to the spindle specified at the start of the block. The
return value (= 1) can be used to control whether the complete block is skipped.
CUST_MULTICHAN
Parameter Meaning
_S_NR Spindle number to which the master spindle is set.
_RET Return value
=0 The block is executed corresponding to the run-in mode.
= 1 The entire block is skipped.
21.4 Milling
21.4.1 General
All settings for machine and setting data of the standard cycles are also applicable for milling
under ShopMill and turning under ShopTurn.
Engraving (CYCLE60)
Multiple edge (CYCLE79), circular position pattern (HOLES2), circumferential groove (SLOT2)
Examples:
=0 for vertical milling machines
=16 for horizontal milling machines, boring mill
A detailed description of the MD52000 is provided in Section:
Activating turning/milling/drilling/grinding technologies (Page 465)
For plane selection when milling, appropriately set the following machine data:
Software option
You require the following software option in order to use this function:
"Transmit and peripheral surface transformation".
Precondition
● There must be at least one rotary axis at the machine.
● The milling tool must be radially oriented to the cylinder to be machined.
Function
The following groove machining operations can be performed with the Cylinder surface
transformation functions:
● Longitudinal grooves on cylindrical bodies
● Transverse grooves on cylindrical objects
● Grooves with any path on cylindrical bodies
The path of the grooves is programmed with reference to the unwrapped, level surface of the
cylinder. Programming can be realized using straight line/circle, drilling or milling cycles or
contour milling (free contour programming).
There are two variants of cylinder surface transformation, i.e.
1. with groove side offset (ON)
2. without groove side offset (OFF)
Axis configuration
&
=
<
You must configure two data sets with the following machine data for the machine illustrated
above:
MD24800 $MC_TRACYL_ROT_AX_OFFSET_1
=0 Offset of rotary axis for the 1st TRACYL transformation.
MD24805 $MC_TRACYL_ROT_AX_FRAME_1
=1 Axial offset of rotary axis for the 1st TRACYL transformation.
MD24810 $MC_TRACYL_ROT_SIGN_IS_PLUS_1
=1 Sign of the rotary axis for the 1st TRACYL transformation.
MD24820 $MC_TRACYL_BASE_TOOL_1[ ]
[0] = 0 Vector of the base tool for the 1st TRANSMIT transformation in XYZ
[1] = 0
[2] = 0
MD24200 $MC_TRAFO_TYPE_2
= 513 Transformer type (513 = cylinder surface transformation with groove side offset)
MD24210 $MC_TRAFO_AXES_IN_2
[0] = 3 Channel axis: Infeed axis perpendicular (radial) to rotary axis Z
[1] = 4 Channel axis: Rotary axis A
[2] = 1 Channel axis: 1st axis of the machining plane parallel to the rotary axis X
[3] = 2 Channel axis: 2nd axis of the machining plane Y
MD24220 $MC_TRAFO_GEOAX_ASSIGN_TAB_2
[0] = 1 Channel axis: 1st geometry axis X
[1] = 4 Channel axis: 2nd geometry axis A
[2] = 3 Channel axis: 3rd geometry axis Z
MD24850 $MC_TRACYL_ROT_AX_OFFSET_2
=0 Offset of the rotary axis for the 2nd TRACYL transformation
MD24855 $MC_TRACYL_ROT_SIGN_IS_FRAME_2
=1 Axial offset for the 2nd TRACYL transformation
MD24860 $MC_TRACYL_ROT_SIGN_IS_PLUS_2
=1 Sign of the rotary axis for the 2nd TRACYL transformation
MD24870 $MC_TRACYL_BASE_TOOL[ ]
[0] = 0 Vector of the base tool for the 2nd TRACYL transformation in XYZ
[1] = 0
[2] = 0
Note
Data sets for transformations
For both data sets, you can use any transformations from all available transformations
(MD24100 $MC_TRAFO_TYPE_1, MD24200 $MC_TRAFO_TYPE_2, etc.). The two data sets
need not be directly next to each other.
However, the 1st data set must always be used for "Cylinder surface transformation without
groove side offset" (= 512) and the 2nd data set for "Cylinder surface transformation with
groove side offset" (=513).
Software options
You require the following software option in order to use this function: "ShopMill/
ShopTurn"
Function
The Multiple clamping function provides optimized tool change over several workpiece
clampings. On the one hand, this reduces downtimes and, on the other, eliminates tool change
times because a tool performs as many machining operations as possible in all clampings
before the next tool change is initiated.
You can either execute the same program several times for the clampings or you can select
different programs. If you are using large-area fixture plates on your machine, you do not have
to set up anything else.
In the case of rotating clamping devices, on the other hand, you must adapt a cycle to match
the features of the clamping device so as to ensure that the next workpiece can be turned to
the machining position after machining of the previous one (or for multiple clamping devices
even while the current workpiece is being machined).
Example
A rotating clamping device (reversible clamping device) is used with four clampings. The
respective clampings can be machined by positioning rotary axis A:
Clamping 1: A = 0°
Clamping 2: A = 90°
Clamping 3: A = 180°
Clamping 4: A = 270°
<
&ODPSLQJ
&ODPSLQJ &ODPSLQJ
5RWDU\D[LV$
&ODPSLQJ
0DFKLQHWDEOH
ENDIF
;
;––––––––––––––––––––––––––––––––––––
_NV=_NPV+_ACT ; Calculate current zero offset
N10 G[8]=_NV ; There must not be a calculation here
RET
21.5 Turning
21.5.1 General
All settings for machine and setting data of the standard cycles are also applicable for milling
under ShopMill and turning under ShopTurn.
Examples:
0: Vertical turning machine (carousel-type turning machine)
19: Horizontal turning machine, machining in front of the turning center
34: Horizontal turning machine, machining behind the turning center (inclined bed turning
machine)
A detailed description of MD52000 is given in Section: "Activating turning/milling/drilling/
grinding technologies (Page 465)."
Bit 4 Enable spindle control of the counterspindle control via user interface
Bit 5 Enable spindle control of the tool spindle via user interface
Bit 6 Enable balance cutting for two-channel stock removal
Bit 7 Retraction when cutting along the contour with G1
Bit 8 Enter the spindle chuck data in the program
Bit 9 Additional input of the tailstock data in the program
Bit 10 Enable crowned thread
Bit 12 Deactivate thread synchronization
Bit 13 Cutting along the contour with CYCLE95 (828D programGUIDE without Advanced Tech‐
nology
Traversing direction
In order that the user interface and cycles know in which direction the spindles and rotary axes
rotate, the following settings must be made.
You set the direction of rotation of an NC rotary axis via MD32100 $MA_AX_MOTION_DIR.
As a result, the following setting options are obtained for the main spindle:
0 0 0 0
0
&
0 1 1 1
0
&
1 1 0 0
& 0
1 0 1 1
& 0
Note
MD52207[n] bit 4 = *)
Bit 4 can be set from the operator's view (values as specified) or according to DIN ("0" and "1"
are then interchanged).
Dimensions
To define the reference point for moving the counterspindle, you must first communicate the
dimensions of the counterspindle. You can either enter the dimensions in the following axis-
specific cycle machine data or in the menu "Parameter" -> Setting data -> Spindle chuck data".
Changes to the machine data are automatically accepted in the menu and vice versa.
Additional settings
The M code, e.g. M34 or M1 = 34 for the spindle chuck is defined in the following machine
data. The manufacturer cycle CUST_TECHCYC.SPF also takes the M functions from the
following machine data:
Software option
You require the following software option in order to use the counterspindle on your
machine:
"Generic coupling 'CP-STATIC'" or higher
Function
If your turning machine has a counterspindle, you can machine workpieces using turning,
drilling and milling functions on the front and rear faces without reclamping the workpiece
manually.
Before machining the rear face, the counterspindle must grip the workpiece, pull it out of the
main spindle, and position it at the new machining position.
Traversing direction
In order that the user interface and cycles know in which direction the spindles and rotary axes
rotate, the following settings must be made.
You set the direction of rotation of an NC rotary axis via MD32100 $MA_AX_MOTION_DIR.
As a result, the following setting options are obtained for the counterspindle:
1 1 0 0
0
&
1 0 1 1
0
&
0 0 0 0
0 &
0 1 1 1
0 &
Note
MD52207[n] bit 4 = *)
Bit 4 can be set from the operator's view (values as specified) or according to DIN ("0" and "1"
are then interchanged).
The display must be the same for the main spindle and the counterspindle ("from operator's
view" or "according to DIN").
Dimensions
To define the reference point for moving the counterspindle, you must first announce the
dimensions of the counterspindle. You can either enter the dimensions in the following axis-
specific cycle machine data or in menu "Parameter" → "Setting data" → "Spindle chuck data."
Changes to the machine data are automatically accepted in the menu and vice versa.
Software option
You require the following software option in order to use the counterspindle on your
machine:
"Generic coupling 'CP-STATIC'" or higher
The position to which the counterspindle travels when the program starts is defined in the
following channel-specific cycle setting data:
The following channel-specific setting data becomes effective when traveling to the fixed stop:
Between traveling to the fixed stop and gripping, the counterspindle can retract a short distance
to counteract compressive stress in the workpiece.
After gripping you can cut off the workpiece. Before doing so, the counterspindle can retract
a short distance with the workpiece to exert tensile stress on the workpiece. This relieves
pressure on the tool when cutting off.
After cut-off, you can carry out a cut-off check and for turning, use the "Travel to fixed stop"
function. You can activate/deactivate the cut-off check using the channel-specific cycle setting
data:
The cut-off is successful when travel to fixed stop fails. The following alarms are output:
You can switch off the alarm display using the following machine data:
You can set this machine data axis-specifically in the "Machine Data" window in the "Tool zero"
operating area.
If, however, the specified force is reached during the cut-off check (i.e. travel to fixed stop is
successful), alarm 61255 "Error during cut-off: Tool break?" is issued.
Note
The "Travel to fixed stop" function can also be used when gripping the spindle (see above). If
travel to fixed stop does not succeed when gripping, an alarm will of course still be issued.
Instead of alarms 20091 and 20094, the alarm 61254 "Error during travel to fixed stop" will be
issued.
Note
MD37050 can also contain values not equal to 2, e.g. 10 = 2 + 8. Make sure that the value 2
is always contained logically so that the monitoring for travel to fixed stop can be hidden. If
MD37050 does not contain the value 2, the cut-off check is not active.
Thread-cutting (CYCLE99)
To correctly machine the thread, it is necessary to set the machine data MD52207
$MCS_AXIS_USAGE_ATTRIB[n] with bit 3, see Chapter: Setting up a counterspindle
(Page 496).
Contour groovingCYCLE930, contour turning CYCLE950, stock removal at corner CYCLE951, contour
turning CYCLE952
Angle
&RQWRXU
$QJOH
&XUUHQWFXWWLQJGHSWK'
5HVLGXDOPDWHULDO
Note
The channel-specific cycle setting data SD55585 is only evaluated if
SD55586 $SCS_TURN_CONT_INTER_RETRACTION = 0.
Example: If the SD is set to 50% and the final machining allowance is 0.5 mm, any residual material less
than 0.25 mm is not removed with the residual machining – but is removed during finishing. If during a
machining step, less residual material is present than defined in the SD, the error message "No material
present" is issued. This means that this residual material roughing step can be omitted because no
machining is performed.
As the tool bends during plunge turning, the tool cannot travel right up to the contour during
stock removal. The lateral distance to the last cut by which the next cut is shortened is specified
in the following channel-specific cycle setting data.
a a
b
X
As the tool bends during plunge turning, the tool would make an excessively deep cut during
stock removal. The retraction distance of the tool between plunge-cutting and stock removal
is specified in the following channel-specific cycle setting data:
General configuration
If driven milling tools are available on a lathe, then the following functions can also be set-up
on this machine:
● Cylinder surface transformation (TRACYL) (Page 505)
● End face machining (TRANSMIT) (Page 508)
Lathe with X and Z axes, main and tool spindle and counterspindle
For example, for a lathe with X and Z axes, main spindle (C1), tool spindle (WZ) and
counterspindle (C2), you can configure the following machine data:
Lathe with X and Z axes, main and tool spindle and Y axis
For example, for a lathe with X, Z and Y axes, main spindle (C1) and tool spindle (WZ), you
can configure the following machine data:
Software option
You require the following software option in order to use this function:
"Transmit and peripheral surface transformation"
Function
Using the cylinder surface transformation function (TRACYL), you can machine the peripheral
surface of a turned part.
Setting up
General settings for cylinder transformation
MD28082 $MC_MM_SYSTEM_FRAME_MASK
Bit 6 = 1 Configuration of the transformation frame for the compensation.
When setting up the functions, you can take the following channel-specific machine data into
account:
Note
You must also set up other machine data for each of the individual transformations.
MD24800 $MC_TRACYL_ROT_AX_OFFSET_1 Offset of the rotary axis for the 1st TRACYL
transformation.
=0
MD24810 $MC_TRACYL_ROT_SIGN_IS_PLUS_1 Sign of the rotary axis for the 1st TRACYL
transformation.
=1
MD24820 $MC_TRACYL_BASE_TOOL_1[ ] Vector of the base tool for the 1st TRACYL
transformation.
[0] = 0
[1] = 0
[2] = 0
MD24800 $MC_TRACYL_ROT_AX_OFFSET_1 Offset of the rotary axis for the 1st TRACYL
transformation.
=0
MD24810 $MC_TRACYL_ROT_SIGN_IS_PLUS_1 Sign of the rotary axis for the 1st TRACYL
transformation.
=1
MD24820 $MC_TRACYL_BASE_TOOL_1[ ] Vector of the base tool for the 1st TRACYL
transformation.
[0] = 0
[1] = 0
[2] = 0
Software option
You require the following software option in order to use this function:
"Transmit and peripheral surface transformation"
Function
Using the end face machining function (TRANSMIT), you can machine the end face of a turned
part.
Setting up
For general settings for transformations, please refer to Chapter "Cylinder surface
transformation (TRACYL) (Page 505)".
You can make additional settings in the following channel-specific machine data:
MD24900 $MC_TRANSMIT_ROT_AX_OFFSET_1
=0 Offset of the rotary axis for the 1st TRANSMIT transformation.
MD24905 $MC_TRANSMIT_ROT_AX_FRAME_1
=2 Axial offset of the rotary axis is taken into account during TRANSMIT 1.
MD24910 $MC_TRANSMIT_ROT_SIGN_IS_PLUS_1
=0 Sign of the rotary axis for the 1st TRANSMIT transformation.
MD24911 $MC_TRANSMIT_POLE_SIDE_FIX_1
=1 Limitation of working range in front of/behind the pole, 1st TRANSMIT.
MD24920 $MC_TRANSMIT_BASE_TOOL_1[ ] Vector of the base tool for the 1st TRANS‐
MIT transformation.
[0] = 0
[1] = 0
[2] = 0
MD24100 $MC_TRAFO_TYPE_1
= 257 Definition of transformation 1 in the channel: TRANSMIT main spindle.
MD24900 $MC_TRANSMIT_ROT_AX_OFFSET_1
=0 Offset of the rotary axis for the 1st TRANSMIT transformation.
MD24905 $MC_TRANSMIT_ROT_AX_FRAME_1
=2 Axial offset of the rotary axis is taken into account during TRANSMIT 1.
MD24910 $MC_TRANSMIT_ROT_SIGN_IS_PLUS_1
=0 Sign of the rotary axis for the 1st TRANSMIT transformation.
MD24911 $MC_TRANSMIT_POLE_SIDE_FIX_1
=1 Limitation of working range in front of/behind the pole, 1st TRANSMIT.
MD24920 $MC_TRANSMIT_BASE_TOOL_1[ ] Vector of the base tool for the 1st TRANS‐
MIT transformation.
[0] = 0
[1] = 0
[2] = 0
For further information, see also Chapter "Clamping a blank (Page 110)".
Note
The face end machining is automatically integrated in the cycles, with the exception of the
straight line and circle.
You can select the functions for these two cycles in the "Program" operating area at "Straight
line" and "Circle".
References
Function Manual Extended Functions; M1: Kinematic transformation,
Section: "TRANSMIT face end transformation"
Software option
You require the following software option in order to use the inclined Y axis function
on your machine:
"Inclined axis"
Function
If your turning machine has an inclined Y axis (i.e. this axis is not perpendicular to axes X and
Z), you can still completely program machining operations in Cartesian coordinates. The
control uses the inclined axis function (TRAANG) to transform the Cartesian coordinates to
the motion of the inclined axis.
Setting up
You still have to set up the inclined axis function (TRAANG) via machine data.
Note
In the user interface, the inclined axis function is automatically integrated in the cycles after
setting up. For machining with inclined axis, in the screen forms of the machining plane, you
can select "Face Y" or "Peripheral surface Y" and enter the Cartesian coordinates.
You will find additional information on the inclined Y axis function in:
References
● Function Manual Extended Functions; M1: Kinematic transformation,
Section: "TRAANG oblique angle transformation"
● Programming Manual, Job Planning, Section "Transformations" > "Kinematic
transformations" > "Inclined axis (TRAANG)"
Example
For example, for a turning machine with X and Z axes and inclined Y axis, main spindle (C)
and tool spindle (WZ), you must configure the following machine data:
MD20110 $MC_RESET_MODE_MASK
Bit 0 = 1 TRAANG is retained after ramp-up.
Bit 7 = 0
MD20112 $MC_START_MODE_MASK
Bit 7 = 1 TRAANG is retained after "Cycle start".
MD20118 $MC_GEOAX_CHANGE_RESET
=1 Allow automatic geometry axis change.
MD20140 $MC_TRAFO_RESET_VALUE
=5 TRAANG always active after reset.
MD20144 $MC_TRAFO_MODE_MASK
Bit 0 = 1 TRAANG runs in the background (persistent) and is not shown on the user interface.
MD20070 $MC_AXCONF_MACHAX_USED[4]
=5 Channel axis YC = 5th machine axis.
MD24430 $MC_TRAFO_TYPE_5
= 1024 Transformation 5: TRAANG
MD24436 $MC_TRAFO_INCLUDES_TOOL_5
=0 Tool handling with active transformation 5.
MD24700 $MC_TRAANG_ANGLE_1
= 55 Angle between 1st and 2nd transformation axis. Data set for linking (TRACON) of end
face machining on main spindle (TRANSMIT) and inclined axis (TRAANG).
Data set for linking (TRACON) of end face machining on main spindle (TRANSMIT) and
inclined axis (TRAANG):
MD24440 $MC_TRAFO_TYPE_6
= 8192 Type of transformation that is available as sixth in the channel.
Data set for linking (TRACON) of cylinder surface transformation on main spindle (TRACYL)
and inclined axis (TRAANG):
MD24450 $MC_TRAFO_TYPE_7
= 8192 Type of transformation 7 in the TRACON channel.
21.6 grinding
General
Grinding tools are identified by tool type 400, 410; dressing tools are identified by tool type
490. The "New tool" function offers these types for selection. The tool list shows the "Grinding
disk" and "Dressing tool" tool types listed according to their tool type. To generate the grinding
disk correction, a tool setter creates a dressing program. Depending on the complexity, the
tool setter makes use of external or internal code generators. This program will be assigned
later to a grinding disk.
Base variant
The dressing is performed in the JOG and AUTOMATIC operating modes, where in automatic
operation, the dressing is called from a part program. To parameterize the dressing, a
diagnostic screen form deployed in manual mode and in the program editor is provided.
The base package offers predefined write contours. The dressing is supported with supplied
screen forms and system cycles. These system cycles are available independent of and
separate from the machining cycles package.
Oscillation cycles
These grinding cycles permit the machining of workpieces with grinding machines using two
geometry axes.
The machines type does not exist because the cycles create only an oscillating movement
that can be used as required on every machine.
This requires a SINUMERIK control as well as fast inputs/outputs for the program processing.
The cycles package provides the following cycles:
● CYCLE4071: Longitudinal grinding with infeed at the reversal point
● CYCLE4072: Longitudinal grinding with infeed at the reversal point and measurement
control
● CYCLE4073: Longitudinal grinding with continuous infeed
● CYCLE4074: Longitudinal grinding with continuous infeed and measurement control
● CYCLE4075: Surface grinding with infeed at the reversal point
References
For further information about oscillating cycles, please refer to:
Programming Manual, Production Planning; Chapter "Programming cycles externally" >
"Technological cycles"
Form-truing (CYCLE495)
21.7 Swiveling
Requirement
The commissioning of the kinematic chain of the machine is a mandatory requirement for
correct swiveling functionality (CYCLE800). The kinematic chain is stored in the tool
parameters $TC_CARR1 to $TC_CARR65.
Note
The vectors of the kinematic chain can be determined with the "Measure kinematics"
measuring function (CYCLE996).
To activate the swivel function, there must be at least one tool holder that can be oriented
(swivel data set) in the NCK, and the workpiece, tool and rotary table reference system frames
must be activated:
Note
Changing machine data MD18088 and MD28082 causes the buffered memory to be
reorganized.
After changing the machine data, a series start-up file must be generated and downloaded,
otherwise, it can be assumed that data will be lost.
To change machine data, you require the following authorization: Access level 1
(manufacturer).
You will find up-to-date information in the following references:
References
● "siemensd.txt" file in the supplied software (standard cycles)
● Function Manual Basic Functions; W1: Tool offset
Section: "Tool holder with orientation capability" > "Oblique machining with 3 + 2 axes"
● Programming Manual, measuring cycles: CYCLE996
Bit 8 Traverse the zero offset for the rotary axes of the swivel data set as offset
= 0 Only take the zero offset for the rotary axes of the swivel data set into account in the WCS
(compatibility)
= 1 Traverse the zero offset for the rotary axes of the swivel data set as offset
Bit 8 is set in conjunction with MD21186.
Bit 9 Swivel data set TC permanently assigned to the tool
= 0 Show number of the swivel data set TC
= 1 Do not show number of the swivel data set TC
The swivel data set is assigned to the tool with parameter SGUD_TC_GNO if technology
MD52200 = 3 is set for cylindrical grinding.
Example:
The machine machine manufacturer can write the current tool _TC_GNO = $P_TOOLNO
into parameter _TC_GNO in the tool change program L6. As a result, the tool holder will
be updated when a tool is changed.
Bit 10 Swivel plane: Show input field "Positioning direction"
= 0 Input field "Positioning direction" is not displayed.
= 1 Input field "Positioning direction" is displayed with swivel table and swivel head/table
combinations.
Bit 11 Positioning both solutions of AB kinematics
= 0 Positions only one solution of some swivel angles (compatibility)
= 1 Positions both solutions calculated by the NC
Bit 11 should be set for kinematics = 1 where, in the kinematics basic setting, neither of
the two rotary axes rotates about the tool axis (AB kinematics in tool axis in the Z direction)
Bit 12 Swivel plane, align tool: Reset behavior takes account of rotary axis positions
= 0 Reset condition refers to the final position of the rotary axes of the swivel data set (com‐
patibility)
Linear axis identifiers are written into parameters $TC_CARR21/22. On reset (TCOABS),
the tool holder is initialized with the final positions of the rotary axes ($TC_CARR13/14).
= 1 Reset condition refers to the current position of the rotary axes of the swivel data set
The rotary axis names of the swivel data set are written into parameters $TC_CARR21/22.
On reset (TCOABS), the tool holder is initialized with the actual values of the rotary axes.
Additional settings
For the swivel function, set the following machine data as a minimum to the following - although
this deviates from the default value:
MD10602 $MN_FRAME_GEOAX_CHANGE_MODE
=1 The actual total frame (zero offsets) is recalculated when switching over geometry axes
(selecting/deselecting TRAORI).
If several channels are declared in the NCU, the number of swivel data sets is split up, taking
MD28085 $MN_MM_LINK_TOA_UNIT into account.
Example 1:
Machine has two channels with different TO units.
Channel 1: MD28085 $MN_MM_LINK_TOA_UNIT= 1
Channel 2: MD28085 $MN_MM_LINK_TOA_UNIT= 2
Three swivel data sets (SDS) are required for each TO unit.
MD18088 = (number of TO units) x (number of SDS per TO unit) = 2 x 3 = 6
Example 2:
Machine has three channels with two different TO units.
Channel 1: MD28085 $MN_MM_LINK_TOA_UNIT= 1
Channel 2: MD28085 $MN_MM_LINK_TOA_UNIT= 2
Channel 3: MD28085 $MN_MM_LINK_TOA_UNIT= 1
One swivel data set (SDS) is required for each TO unit.
MD18088 = (number of TO units) x (number of SDS per TO unit) = 2 x 1 = 2
Note
If, after a RESET from the NC, a frame must be calculated in the tool direction, then
MD20150 $MC_GCODE_RESET_VALUES[52] can be set to a value > 1.
Applications:
● Machine kinematics with Hirth joint
● Angular tool with basic tool orientation
MD20196 $MC_TOCARR_ROTAX_MODE Rotary axis mode for tool holders with ori‐
entation capability
Bit 0 = 1 Swivel data set with a rotary axis
used for a rotary table with C axis
Bit 1 = 1 Swivel data set with two rotary axes
used for standard swiveling
If several swivel data sets are declared per channel, and if machine functions need to be
activated on changeover between swivel heads or tables, an M command can be issued in
the PLC program on switchover to another swivel data set.
Example
With the output of the M commands, the PLC can limit or invert the spindle speed or clamp or
release the rotary axes, for example.
When used for measuring or swiveling in JOG, the workpiece reference must be active at
RESET and not cleared (cascaded measuring).
Application: Zero offset G5xx, including all rotations, should remain active after Power On.
Axial machine data for the modulo rotary axes of the swivel data set
= 0 As programmed
= 1 Along the shortest path
Application: With the setting bit 2=1, the rotary axis C travels along the shortest path for G90
with DC. For further information, refer to Chapter "Manufacturer cycle CUST_800.SPF
(Page 548)".
Note
Identification of the machine kinematics (kinematic chain) according to DIN 66217 or ISO
841-2001
This checklist does not claim to be complete.
● Do the three linear axes of the machine that are active for the transformation form an
orthogonal coordinate system? Geometry axes XYZ
● How many swivel kinematics does the machine have?
Combinations of two (or one) rotary axis and the three linear axes are always formed.
● Which kinematics type is it?
Swivel head, swivel table or mixed kinematics of swivel head and swivel table.
● What are the names of the rotary axes of the kinematics?
Manual rotary axes are permitted and do not have to be declared in the NC.
● What is the 1st or 2nd rotary axis of a swivel data set?
Rule: Rotary axis 2 is based on rotary axis 1. With mixed kinematics, rotary axis 1 is always
the axis for the tool orientation.
● Is the traversing direction of the linear axes and the rotary axes correct? Right-hand rule
Rule: If the linear axis or the rotary axis moves the workpiece, the direction of motion of the
axis and also the sign of the rotary axis vector change.
● What is the initial setting of the kinematics?
This defines the tool orientation and the plane G17, G18, G19.
● Which rotary axis rotates around which axis of the coordinate system or the machine axis
(axes)?
This defines the rotary axis vectors of the kinematics.
Example 1:
Head kinematics. Rotary axis 2 rotates around axis Y → rotary axis vector V2xyz = 0,1,0
Example 2:
Table kinematics. Rotary axis 1 rotates around axis X → rotary axis vector V1xyz = -1,0,0
The parameters of the swivel data set ($TC_CARR1[n] to $TC_CARR65[n]) can be read-in
and read-out in the startup operating area. Programming with appropriate value assignment
is also possible in an NC program (manufacturer cycle). The parameters of the swivel data set
are immediately effective after the program has started.
The following softkeys are assigned to the Swivel function in the "Program" → "Various"
operating area:
The "Align turning tool" and "Align milling tool" softkeys are only displayed if the "B-axis
kinematics" function has been activated via $TC_CARR37[n].
Offset vectors I1 to I4
The vectors always contain three components which represent the reference to the machine
axes (X, Y, Z). The positions in the kinematic chain are measured by the machine
manufacturer; they are always relevant with respect to a swivel head / swivel table (swivel data
set). Offset vectors I1 to I4 refer to the non-swiveled state of the rotary axes (machine
kinematics basic setting).
The machine kinematics used do not need to be fully implemented. However, be aware that
the traversing range in the swivel planes may be restricted. If machine kinematics are to be
implemented with just one rotary axis, this must always be declared as the 1st rotary axis.
References
You can find additional information in:
● Function Manual Basic Functions; Tool Offset (W1)
● Function Manual Special Functions; Multiple Transformations (F2)
Figure 21-4 Dialog to input parameters for the swivel data set
If several swivel data sets are declared in each NC channel, then a name is assigned to each
swivel data set. $TC_CARR34[n]
No name needs to be specified if the swivel-mounted tool carrier is not exchangeable (i.e. one
swivel data set per channel).
The name of the swivel data set may only contain characters that are permissible for NC
programming: A...Z, 0...9 and _ !
If several NC channels have been set up, note the settings in MD28085, Chapter "Technology
cycles for swiveling (Page 517)". If a TO unit is assigned to several NC channels, the channel
display in the dialog corresponds to the TO unit.
restricted. If machine kinematics are to be implemented with just one rotary axis, this must
always be declared as the 1st rotary axis.
Manually adjustable rotary axes (manual mode) are possible with and without measuring
systems and can be used with "simple machines".
Rotary axes that are positioned by an additional mechanical system, can be declared in the
"Semiautomatic" mode.
Example
In a boring mill, the swivel head is positioned by coupling the spindle. In this case, the rotary
axes of the swivel head must be declared as "Semiautomatic". The appropriate machine-
specific cycles are called in CUST_800.SPF.
Machine manufacturer
Please refer to the machine manufacturer's specifications.
Swivel head
● I3 distance from the tool adapter to the pivot point/intersection of the 2nd rotary axis
● I2 distance from the pivot point/intersection of the 2nd rotary axis to the pivot point/
intersection of the 1st rotary axis
● I1 closure of the I1=-(I2+I3) vector chain, if the swivel head cannot be changed
Swivel table
● I2 distance from the machine reference point to the pivot point/intersection of the 1st rotary
axis
● I3 distance from the pivot point/intersection of the 1st rotary axis to the pivot point/
intersection of the 2nd rotary axis (or to the reference point of the tool adapter)
● I4 closure of the I4=-(I2+I3) vector chain, if the swivel table cannot be changed
In the case of machine kinematics that move the workpiece (rotary table), the axis direction is
reversed.
Note
Interrelation of TOOLCARRIER ⇔ 5-axis transformation (transformer type 24, 40, 56):
For 5-axis transformation, transformer type 72 in MD24100: $MC_TRAFO_TYPE_1 can be
used.
In the case of transformer type 72, the vectors of the TOOLCARRIER in MD24582:
$MC_TRAFO5_TCARR_NO_1 are used.
$TC_CARR41[n] to $TC_CARR60[n]
I1 $TC_CARR1..3[n] to $TC_CARR41..43[n]
I2 $TC_CARR4..6[n] to $TC_CARR44..46[n]
I3 $TC_CARR15..17[n] to $TC_CARR55..57[n]
I4 $TC_CARR18..20[n] to $TC_CARR58..60[n]
The fine offsets act in addition to the corresponding base vectors when the Swivel function
CYCLE800 or the NC function TCARR=n is called.
The following identifiers should be preferably chosen for the names of the rotary axes:
● Rotary axis rotates around machine axis X → A
● Rotary axis rotates around machine axis X → B
● Rotary axis rotates around machine axis Z → C
For automatic rotary axes, the channel names of the corresponding NC rotary axes must be
entered (see $TC_CARR37[n] TENS and HUNDREDS position: Automatic mode). For manual
(manually adjustable) and semiautomatic rotary axes, you can use any axis identifier (up to
six letters or digits).
Manual and semiautomatic rotary axes are not defined in the NC. With manual rotary axes,
the value for the angular range is entered in the dialog box. Semiautomatic rotary axes are
moved mechanically on the machine, e.g. through a coupled spindle. The adaptations for this
can be made in the CUST_800 manufacturer cycle. The value for the angular range must not
be specified, the rotary axis positioning is performed automatically.
Machine manufacturer
Please refer to the machine manufacturer's specifications.
Align tool
● For "Align tool", the programming of beta and gamma is machine-independent.
● With the basic position setting "Working plane" or "-Z", beta = 0 also corresponds to this
basic position (compatibility).
● With the basic position setting "-X", the B axis is re-oriented through 90° for beta = 0.
Select the retraction variant in the input field: This is defined in the ONE MILLION and TEN
MILLION position of the system variable $TC_CARR37[n]:
● Retract axis Z
● Retract axes Z, XY
● Retract in the tool direction, maximum or incremental
NOTICE
Collision avoidance
Make sure that the tool and the workpiece cannot collide during swivelling when moving the
tool axes.
The type of retraction is modified in the Manufacturer cycle CUST_800.SPF (Page 548).
Note
Retraction in the tool direction is useful for swivel data sets in which the tool is re-oriented
(swivel head or mixed kinematics). This applies particularly for turning machines with a B axis.
During retraction in "maximum tool direction", traversing is performed until one of the relevant
linear axes reaches the software limit switch.
21.7.4 Examples of machine kinematics for the commissioning of the Swivel function
<
;
,
&
,
$
,
/
/ WRROOHQJWK
Figure 21-7 Exchangeable swivel head with steep taper to hold the spindle
5RWDU\D[LV
9
9
JUG
,
, 5RWDU\D[LV
, &HQWHURIURWDWLRQRI
URWDU\D[LV =
&HQWHURIURWDWLRQ
RIURWDU\D[LV <
5HIHUHQFHSRLQW ;
RIWRRO
Figure 21-8 Cardanic swivel head with Hirth joint, manually adjustable
The vectors in the drawing refer to the initial setting of the kinematics. The spindle (tool adapter)
is positioned on a gage block above the top edge of the table/center of the table (rotary axis
C). A test mandrel in the spindle is used to determine the center of rotation of rotary axis C.
5HIHUHQFHSRLQWRIWKHPDFKLQH
0.6;<=
9 ,
,]
,\
,
¡
,]
,
5RWDU\D[LV& 5RWDU\D[LV%
=
9
<
;
The vectors in the drawing refer to the initial setting of the kinematics. The spindle (tool adapter)
is positioned on a gage block above the top edge of the table/center of the table (rotary axis
C). A measuring rod in the spindle is used to determine the turning center of rotary axis C.
9
=
5RWDU\D[LV%
<
; O
O]
O O O
O\
The vectors in the drawing refer to the initial setting of the kinematics. The spindle (tool adapter)
is positioned on a gage block above the top edge of the table/center of the table (rotary axis
C). A measuring rod in the spindle is used to determine the turning center of rotary axis C.
9
<
; 5RWDU\D[LV&
O
O
O\
O
O\ 5RWDU\D[LV$
5HIHUHQFHSRLQWRI 9
WKHPDFKLQH
0.6;<=
9
=
<
;
5RWDU\D[LV&
O O O
O ,,
O]
O
O[ 5RWDU\D[LV$ 9
5HIHUHQFHSRLQWRI
WKHPDFKLQH
0.6;<=
References
Function Manual Basic Functions; W1: Tool offset, parameter CUTMOD:
● The CUTMOD NC function is activated when data set 2 is called in the NC program
(CYCLE800 align turning tool). This means that the cutting edge position or the tool
reference point is updated corresponding to the tool orientation:
● When calling a swivel data set for rotational operation in the NC program (CYCLE800 align
tool), the CUTMOD NC function is activated. The cutting edge position, tool angle, cut
direction and tool reference point are thus calculated in accordance with the current tool
orientation following the "Align tool" function.
Function
During swiveling, all axis positions are approached using the CUST_800.SPF cycle. The call
is exclusively made from the swivel cycle CYCLE800 or from the cycles
E_TCARR (ShopMill) or F_TCARR (ShopTurn).
In cycle CUST_800.SPF, the function markers (_M2: to _M59) are prepared and documented.
Also refer to the following "Structogram CYCLE800".
There are extensions in the CUST_800.SPF cycle for the "Turning on milling machine" function,
see Chapter "Adaptations for CUST_800 (Page 566)".
Note
If you modify the CUST_800, ensure that the G commands of the G groups used are restored
at the end of the CUST_800 (versions S_G_1 to S_G_5!).
Parameter
CUST_800 (INT _MODE, INT _TC1, REAL _A1, REAL _A2, INT _TC2, REAL _T_POS)
&867B63)
/DEHOB0B0
(B7&$5563)
)B7&$5563)
&<&/(63) /DEHOB0B0
(QGRIF\FOH
6WUXFWXUH&<&/(63) &867B63)
,QSXWSDUDPHWHUV
QDPHRIVZLYHOGDWDVHW
PRGH
RIIVHWV
URWDWLRQV
UHWUDFWLRQ
&DOFXODWLRQRI ,QLW
YDOLGVZLYHOGDWDVHW /DEHOB0,QLW 5HZULWHYHFWRUV
NLQHPDWLFFKDLQLVSRVVLEOH
IRUH[DPSOHWHPSHUDWXUHFRPSHQVDWLRQ
YHFWRUVRULQFOXVLRQRI
6ZLYHOGDWDVHWLQYDOLG :D[LVLQGULOOLQJWRROV
)DXOWPHVVDJHV
5HWUDFWLRQ $GDSWDWLRQRI
/DEHO
7RROD[LV UHWUDFWLRQVWUDWHJ\
B0=D[LV
B0=D[LV;<
D[LV
B0PD[WRROGLUHFWLRQ
B0WRROGLUHFWLRQLQF
1RUHWUDFWLRQ
7UDYHUVHURWDU\D[HVIRU1&D[HV
/DEHO
FDOFXODWLRQRIWKH B0VZLYHOURWDU\D[HVDXWRPDWLFDOO\
URWDU\D[LVDQJOH B0VZLYHOURWDU\D[LVDXWRPDWLFDOO\
GLVSOD\DQJOHYDOXHVWREHVHW URWDU\D[LVPDQXDOO\RUVHPLDXWRPDWLFDOO\
PDQXDOURWDU\D[HV B0VZLYHOURWDU\D[LVDXWRPDWLFDOO\
GHDFWLYDWHD[LVWUDQV B0VZLYHOURWDU\D[LVPDQXDOO\RUVHPLDXWRPDWLFDOO\
IRUPDWLRQ B0VZLYHOURWDU\D[LVDXWRPDWLFDOO\
URWDU\D[LVPDQXDOO\RUVHPLDXWRPDWLFDOO\
B0VZLYHOURWDU\D[HVPDQXDOO\RU
VHPLDXWRPDWLFDOO\
1RWUDYHUVLQJ B0B0B0VZLYHOLQ-2*ZLWK75$25,
RIURWDU\D[HV
(QGRIF\FOH
6'6!6ZLYHOGDWDVHW
\HV
2OG6'6
1HZ6'6"
QR
QR
QR
$XWRPDWLFDOO\ /DEHOB0$XWRPDWLFDOO\FKDQJH
FKDQJH \HV VZLYHOKHDGWDEOH"
6'6ROG /DEHOB0$XWRPDWLFDOO\FKDQJH
0DQXDOO\FKDQJH VZLYHOKHDGWDEOH"
6'6QHZ"
QR
/DEHOB00DQXDOO\FKDQJH
0DQXDOO\FKDQJH \HV VZLYHOKHDGWDEOH"
6'6ROG"
$XWRPDWLFDOO\FKDQJH /DEHOB0$XWRPDWLFDOO\FKDQJH
6'6 VZLYHOKHDGWDEOH"
QHZ"
QR
\HV /DEHOB0&KDQJHPDJD]LQHWRRO
7RRO
FKDQJH" B0&KDQJHPDQXDOWRRO
QR /DEHOB06ZLYHODIWHUWRROFKDQJH$872
B06ZLYHODIWHUWRROFKDQJH-2*
/DEHOB05HWUDFWLRQDIWHUVZLYHOLQJ
(QGRIF\FOH
Modification examples
If the rotary axes (swivel head/table) are not to be positioned during swivel data change / tool
change, the call of the E_SWIV_H cycle can be commented out at the relevant markers. If the
rotary axes are to move to a certain position, an angle value can be transferred to parameters
Par 2, Par 3.
Function
With the Measure kinematics function, it is possible to calculate the geometric vectors used to
define the 5-axis transformation (TRAORI and TCARR) by measuring the position of the ball
in space.
The measurement is essentially carried out by means of workpiece probes, which scan three
positions of a measuring ball on each rotary axis. The ball positions can be defined in
accordance with user specifications so that they correspond to the geometric ratios on the
machine. The only way of setting the ball positions is to reposition the rotary axis that is to be
measured in each case.
Aside from the basic mechanics of the machine, no specific knowledge is required to use
CYCLE996. No dimension drawings or machine location diagrams are necessary to carry out
measuring.
Application range
The Measure kinematics function (CYCLE996) can be used to determine the data that is
relevant to transformations in the case of kinematic transformations that involve rotary axes
(TRAORI, TCARR).
Options:
● Redetermination of swivel data sets
– Commissioning the machine
– Use of swivel-mounted workholders as TCARR
● Checking swivel data sets
– Service following collisions
– Checking the kinematics during the machining process
Kinematics with manual axes (manually adjustable rotary tables, swivel-mounted workholders)
can be measured in the same way as kinematics with NC-controlled rotary axes.
When CYCLE996 is started, a swivel data set with basic data (for kinematics type) must be
parameterized. The measurement itself must be carried out without an active kinematic
transformation.
If, in the setting data SD55740 $MNS_MEA_FUNCTION_MASK bit 7 is set, then depending
on the setting, the kinematics can be measured based on the calculated or on the rotary axis
vectors saved in the swivel data set.
Requirements
The following requirements must be met in order to use CYCLE996 (Measure kinematics):
● SIEMENS measuring cycles package is installed
● Workpiece probe is calibrated
● Calibration ball is mounted
● Oriented tool carrier is set up (MD18088 MM_NUM_TOOL_CARRIER > 0)
● The basic geometry of the machine (X, Y, Z) is rectangular and referenced
The right angle refers to the workpiece spindle and should be preferably checked using a
test mandrel.
● Defined position of the rotary axes involved in the transformation
● Defined traverse directions in compliance with the standard of all axes involved in the
transformation according to ISO 841-2001 and/or DIN 66217 (righthand rule)
● Defined size of the protocol file (MD11420 $MN_LEN_PROTOCOL_FILE ≥ 20)
The precise procedure when measuring and programming, including examples, is described
in the following manual:
References
Programming Manual, Measuring Cycles: CYCLE996
Machine manufacturer
Please refer to the machine manufacturer's specifications.
Setting up parameters
Machine data
Set the following machine data to set up the technology:
Note
If you use angular tools (type 130) with variable tool orientation, you require the setting
MD18114 = 3.
MD20112 $MC_START_MODE_MASK Definition of the basic control setting after part pro‐
gram start
Bit 7 = 0 The current setting for the active transformation is retained.
Note
Only set bit 1 in MD52214 when a fixed table is used in addition to a rotary table.
Note
Depending on the set mounting alignment in MD52242, different parameters are available in
the "Align Turning Tool" dialog.
Setting data
The following setting data is recommended: Set the setting data to set up the technology:
NOTICE
Risk of collision
Value changes of SD42940, SD42942 and SD42950 during the program execution can cause
collisions. Only set the setting data during the commissioning.
Note
SD42942 is only evaluated after setting SD42950.
Additional settings
● Set the current zero point in the center point of the turning tool, e.g. via a settable zero
offset.
● Change the tool before the "Align turning tool" cycle call.
● Program the tool in the part program for the simulation.
Note
No tool is active after the start of the simulation.
● After the "Align turning tool" cycle call, traverse the tool to Y = 0.
● Limit the maximum speed of the tool spindle, e.g. with the tool change cycle, in order to
avoid too high a speed of the turning tool.
● The turning tools in the tool management are automatically set up by the system. You can
make your own modifications in file sltmmillturnlistconfig.xml, for example, for the OEM tool
list.
Requirement
A kinematic chain is already available for the machine.
For further information on kinematic chaining, see Chapter "Kinematic elements (Page 269)".
Setting up parameters
Set the following machine data to set up the kinematics transformation technology:
Behavior at reset
Make the following settings so that the kinematics transformation is retained after reset and
the turning tool can be used in JOG mode:
MD20112 $MC_START_MODE_MASK Definition of the basic control setting after part pro‐
gram start
Bit 7 = 0 Start behavior, "active kinematics transformation"
Behavior at power on
In order to retain the kinematics transformation after a power on, you must also make the
following additional settings:
Note
The CUTMODK function cannot be retained after power on.
Procedure
Note
The clamping angle is stored in the $TC_DPROT cutting edge parameter.
Settings
$NT_CNTRL[n]
Bit 5 = 1 Swivel axis has a Hirth joint
[n] transformation name
$NT_CNTRL[n]
Bit 6 = 1 Tool spindle has a Hirth joint
[n] transformation name
Settings
Set the appropriate coordinate system via the following channel-specific machine data (values,
for example, for boring mills):
Describe the rotation of the coordinate system as follows at the _M70 marker in the
CUST_800.SPF cycle:
Function markers
_M40: ; User Init
N800400 SETMS(1) ; Sets tool spindle as main spindle
N800401 DIAMOF ; No transverse axis defined as diameter
programming for milling
GOTOF _MEND
$OLJQWXUQLQJWRRO 'HVHOHFWWXUQLQJ
&<&/( &<&/(
&<&/( &<&/(
*75$)22) 75$)22)
GHOHWH GHOHWH
:3)UDPH :3)UDPH
&867B &867B
6(706 6(706
',$021 ',$02)
*
75$)221
5(7
&<&/(
&867B
RU
&867B
RU
&867B
RU
&867B
5HWUDFWLRQ
&DOFXODWLRQRI
75$)221
&867B
7UDYHUVH
D[HV
*
7ZLVW
&8702'.
&867B
5(7
Procedure
Read out the position value of the rotary axis via the following system variable:
Note
So that the old rotary axis position is not swiveled in, start the block search in the G code
program after the block for the turning tool alignment.
Function
The High Speed Settings function (CYCLE832) is used to preset data for the machining of
sculptured surfaces so that optimum machining is possible. The call of CYCLE832 contains
three parameters:
● Tolerance
● Machining type (technology)
● Input of the orientation tolerance
The 3rd parameter is significant only for machines with multi-axis orientation transformation
(TRAORI). By default, it is assigned the value 1.
Software option
To use this function, you need the software option:
"Advanced Surface"
For machines for which the orientation tolerance is not significant, the cycle setting data
SD55441 to 55443 can be set to a value of 0. No orientation tolerance is then calculated in
CYCLE832 (OTOL= -1).
Note
During the optimization of the machine axes, the values (note array index) of the specified
machine data must be set correctly.
Function
In contrast to the settings (G functions) by CYCLE832.SPF, these settings can be modified in
the manufacturer cycle CUST_832.SPF.
The following markers are prepared in CUST_832.SPF:
Take into account more than three rotary axes (orientation axes) in CYCLE832
In CYCLE832, a maximum of three rotary axes of the orientation transformation (TRAORI) are
taken into account for FGREF. If more than three rotary axes are declared per channel for the
orientation transformation, you can write the value to FGREF using the following syntax in the
CUST_832:
FGREF[AA]=$AA_FGREF[C]
C = rotary axis 1 (axis is taken into account by CYCLE832)
AA = rotary axis 4
In the manufacturer cycle CUST_832.SPF, parameter _MOTOL is available for the evaluation
of the "Multi-axis programming yes/no".
With the following setting data, additional G functions can be programmed in CUST_832.SPF
for using multi-axis programming:
Example
Using _MOTOL in CUST_832.SPF for the marker for finishing:
_M_FINISH:
IF _MOTOL==1 ; if multi-axis programming
ORISON
ELSE ; no multi-axis programming
ORISOF
ENDIF
...
Function
Besides Advanced Surface, the High Speed Settings (CYCLE832) function also offers the
extension Top Surface. You can use Top Surface to improve the quality of free-form surfaces.
If set actively, the continuous-path control is optimized within contour tolerances. The
CYCLE832 call also contains the smoothing parameter.
Software option
To use this function, you need the software option:
"Top Surface"
Setting up parameters
Set the following setting data to set up the the Top Surface extension:
Depending on the machining type used, the following G commands of G group 59 are
programmed:
DYNFINISH
DYNSEMIFIN
DYNROUGH
Requirement
Two types of electronic probes are used for measuring:
● Probe to measure the workpiece
● Probe to measure the tool
The electronic probe must be connected to the NCU 7x0.
The electronic probe is called probe in the following document
References
NCU Manual: Digital inputs / outputs
DB 10
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Probe actuated
DBB107 Probe 2 Probe 1
To test the switching behavior and the measured value transfer, use an NC test program with,
for example, the following NC commands:
Note
After changing this machine data, the probe must be re-calibrated.
Bit 1 Coupling the spindle alignment with coordinate rotation in the active plane, for workpiece
measurement with multiprobe in the automatic mode
Bit 2 Direction of rotation of the spindle positioning for workpiece measurement regarding active
coupling of the spindle alignment with coordinate rotation in the active plane
Bit 3 For workpiece measurement, number of repeat measurements if the probe does not switch
Bit 4 Measuring feedrate for workpiece measurement
Bit 5 Retraction velocity from the measuring point for workpiece measurement
Bit 6 Workpiece measurement: probe activation/deactivation when positioning the spindle
Bit 7 Measure kinematics, scaling basis for the orientation vectors
Bit 8 Measure kinematics, measurement with active TRAORI or TCARR (CYCLE 800)
Bit 9 User-specific scaling of the rotary axis vectors V1xyz and V2xyz
Bit 15 Workpiece measurement: calibration in the bore with known or unknown center point, meas‐
uring in JOG
Bit 16 Collision monitoring for tool measurement
Bit 17 Tool measurement: number of repetitive measurements if the probe does not switch
Bit 19 Retraction velocity from the measuring point for tool measurement
Bit 28 Continuous measuring standard log in JOG (attach)
Bit 29 Table format for measuring standard log in JOG
Function
The CUST_MEACYC.SPF is part of the measuring cycle functionality. It is called in every
measuring cycle before and after executing the measurement task. The CUST_MEACYC.SPF
acts in the same way when measuring in the JOG mode and measuring in the AUTOMATIC
mode.
You can use the CUST_MEACYC.SPF to program and execute sequences that are necessary
before and/or after a measurement (e.g. activating/deactivating a probe).
Note
Copy the CUST_MEACYC cycle from the NC data/Cycles/Standard cycles directory to the NC
data/Cycles/User cycles directory before making any changes. Changes for CUST_MEACYC
only take effect in this directory.
CUST_MEACYC structogram
Sequence in the AUTOMATIC mode, using measure bore as example, CYCLE977 with probe
type 712.
6WUXFWXUH&<&/( &867B0($&<&
,QSXWYDOXHV B02'( JHQHUDWHGE\PHDVXULQJF\FOH
PHDVXULQJYDULDQW -XPSWRODEHO
VSHFLILFVHWWLQJV B0
EHIRUHZRUNSLHFHPHDVXUHPHQW&<&/(
RIIVHWW\SH
XVHUVSHFLILFHQWULHVIRUH[DPSOHFRRODQWRII
RIIVHWWDUJHW *272)B$0B:3B0(6
ಹ
VHWSRLQW
B$0B:3B0(6
PRQLWRULQJSDUDPHWHUV EHIRUHZRUNSLHFHPHDVXUHPHQW
ಹ
0
SUHSDUDWLRQRIPHDVXUHPHQW
FDOFXODWLRQV
SRVLWLRQLQIURQWRIWKHVW
PHDVXULQJSRLQW B02'( JHQHUDWHGE\PHDVXULQJF\FOH
-XPSWRODEHO
B0($&<&B072))21
XVHUVSHFLILF1&FRPPDQGV
WRGHDFWLYDWHWKHSUREH
IRUH[DPSOH0RU+FRPPDQGV
6' \HV ಹ
6&6B0($B)81&7,21B0$6.%LW 6326 SRVLWLRQVSLQGOH
4XHULHGEHIRUHHDFKIXUWKHU ಹGHILQHGE\F\FOH
6326 ಹ ಹ
B0($&<&B0721
XVHUVSHFLILF1&FRPPDQGV
WRDFWLYDWHWKHSUREH
IRUH[DPSOH0RU+FRPPDQGV
QR 5(7
Requirements
You have already made the settings from the previous Chapter "Measuring cycles and
measurement functions, general (Page 575)".
Workpiece measurement
For milling:
● The probe has been inserted in the tool spindle.
● The probe has been selected in the tool list as type 7xx (probe).
● The probe is activated as tool in the current NC channel.
Tool measurement
To measure tools, an appropriate probe must be located in the machine space so that this can
be reliably and safely reached with a tool in the spindle.
The following tool types are supported with measure tool:
● Milling technology: Tool types 1xx and 2xx
● Turning technology: Tool types 5xx, 1xx and 2xx
For the specified tool types, the tool lengths and the tool radii can be measured.
The following channel-specific machine data is only effective if the system frame actual value
setting and scratching is set up using the above mentioned machine data
MD28082 $MC_SYSTEM_FRAME_MASK, bit 0 = 0.
Note
If you create the conditions described in this section and you have set and checked the machine
setting data, then in JOG mode, you can measure a workpiece using a workpiece probe at a
milling machine!
In JOG mode, you can measure a tool using a tool probe at a milling machine or lathe!
A description is provided in the following chapters as to which settings you can make in order
to adapt measuring to the specific requirements of your particular machine.
Note
Measuring feedrate for workpiece measuring
All measuring cycles use the value saved in SD54611 as the measuring feedrate value
following calibration of the workpiece probe. A different measuring feedrate can be assigned
for each calibration field [n].
When calibrating the probe, either the measuring feedrate from SD55630
$SCS_MEA_FEED_MEASURE is used, or the measuring feedrate can be overwritten in the
input screen when calibrating. To do this, SD54760 $SNS_MEA_FUNCTION_MASK_PIECE
bit 4 must be set to 1.
Note
Measuring feedrate for tool measuring
All measuring cycles use the value saved in SD54636 or SD54651 as the measuring feedrate
after the tool probe has been calibrated. A different measuring feedrate can be assigned for
each calibration field [n].
When calibrating the probe, either the measuring feedrate from
SD55628 SCS_MEA_TP_FEED_MEASURE is used, or the measuring feedrate can be
overwritten in the input screen when calibrating. To do this,
SD54762 $SNS_MEA_FUNCTION_MASK_TOOL bit 4 must be set to 1.
In the following setting data, index [k] stands for the number of the current data field (probe
number -1) of the probe.
The following setting data is used to define in which axes and directions it is possible to calibrate
a tool probe.
Decimal place
ONES 1. Axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
TENS 2. Axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
HUNDREDS 3. Axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
Example
If the general setting data SD54632 $SNS_MEA_T_PROBE_ALLOW_AX_DIR[k] has the value
123, the tool probe is calibrated as follows in the G17 plane:
● X in both directions
● Y only in plus direction
● Z only in minus direction
Note
If the spindle is already rotating when the measuring cycle is called, this direction of rotation
remains independent of the setting of this data.
Note
Feedrate factor 2 should be less than feedrate factor 1.
EQ
E
E
E
General cycle setting data for correction using the correction tables when forming measurements with
rotating spindle.
Note
Measuring feedrate for tool measuring
All measuring cycles use the value saved in SD54636 or SD54651 as the measuring feedrate
after the tool probe has been calibrated. A different measuring feedrate can be assigned for
each calibration field [n].
When calibrating the probe, either the measuring feedrate from SD55628 is used, or the
measuring feedrate can be overwritten in the input screen when calibrating. To do this,
SD54762 $SNS_MEA_FUNCTION_MASK_TOOL bit 4 must be set to 1.
Measure workpiece
For manual measuring functions in the JOG operating mode, for which a rotating spindle is
required, the following applies:
● The channel state must be reset at the instant in time that the measured value is transferred.
● The spindle can be moved or positioned either using the T,S,M menu or using the bits in
DB3x.DBB30.
● The following preconditions apply when using the DB3x.DBB30 technology functions with
fixed speed:
Note
The entry in SD43200 $SA_SPIND_S is kept at power on.
With these settings, the spindle velocity for manual operation, which is set in SD41200
$SN_JOG_SPIND_SET_VELO, is no longer effective.
Requirement
Software option
In order to use the "Measuring in AUTOMATIC" function, you require the software
option: "Measuring cycles"
You have already made the settings from Chapter "Measuring cycles and measurement
functions, general (Page 575)".
Workpiece measurement
Sequence in milling technology:
1. The probe has been selected in the tool list as type 7xx (probe).
2. The probe has been inserted in the tool spindle.
3. The probe is activated in the actual NC channel.
Tool measurement
To measure tools, an appropriate probe must be located in the machine space so that this can
be reliably and safely reached with a tool in the spindle.
The following tool types are supported with tool measurement:
● Milling technology: Tool types 1xx and 2xx
● Turning technology: Tool types 5xx, 1xx and 2xx
For the specified tool types, the tool lengths and the tool radii can be measured.
SD55614 $SCS_MEA_RESULT_MRD Setting of the program control of the measurement result dis‐
play MRD
=0 Switch off the measurement result display
=1 Switch on the measurement result display
References
Programming Manual, Measuring Cycles; Section "Description" > "Behavior on block search,
dry run, program testing, simulation"
Note
If you have created the prerequisites described in this chapter and you have set and checked
the machine/setting data, you can perform measurements at the machine with a workpiece or
tool probe in the AUTOMATIC mode!
If you wish to set up workpiece measurement on a turning machine, then additional settings
are required. Refer to Chapter "Measuring workpieces at the turning machines (Page 602)"
for the settings.
If you wish to set-up tool measurement using a tool probe, then you must also make additional
settings. Please refer to Chapters "Measuring tools at the turning machines (Page 603)" or
"Measuring tools at the milling machines (Page 596)" for the settings.
A description is provided in the following chapters as to which settings you can make in order
to adapt measuring to the specific requirements of your particular machine.
Requirement
You have already made the settings from the following section:
See also: Measuring cycles and measurement functions, general (Page 575)
Settings
General cycle setting data
Note
Measuring feedrate for workpiece measuring
All measuring cycles use the value saved in SD54611 $SNS_MEA_WP_FEED[n] as measuring
feedrate after the tool probe has been calibrated.
A different measuring feedrate can be assigned for each calibration field [n].
When calibrating the probe, either the measuring feedrate from SD55630
$SCS_MEA_FEED__MEASURE is used, or the measuring feedrate can be overwritten in the
input screen when calibrating. To do this, SD54760 MEA_FUNCTION_MASK_PIECE bit 4
must be set to 1.
This angle is added to the angle that the user entered between the workpiece reference edge and the
1st axis of the active coordinate system in a positive direction, and refers to the corner measurement in
the automatic mode (CYCLE961).
The angle that the user enters has the designation "α0" in the parameterizing screen form, corner
measurement. For compatibility programs, the designation is _STA1.
Notice:
For compatibility programs, $SCS_MEA_EDGE_SAVE_ANG should be set = 10.
Settings
The following cycle setting data are written to by the measuring cycles with the "Calibrate
probe" measuring function. User parameterization is not necessary here. However, after the
probe has been calibrated, you can check these values and if required, evaluate the probe
quality, e.g. for position deviations, no values > 0.1 mm should be reached. Otherwise, the
probe must be mechanically readjusted.
The measuring feedrate at the time of calibration is used for all subsequent applications of the
measuring cycles.
Note
Observe the manufacturer's instructions for the probe.
Settings
Calibration data of the tool probe, referred to the machine coordinate system
Before calibration is started, the position of the tool probe in the machine coordinate system
(MCS) must be entered into the following general cycle setting data. In this case, the reference
point is the outer diameter or the tool length of the active tool in the spindle. If there is no tool
in the spindle, the reference points are the spindle center point and the tool reference point at
the spindle.
Note
Calibrate probe
If you have calibrated the tool probe in JOG mode, then the calibration data has already been
correctly entered in: SD54632 $SNS_MEA_TP_AX_DIR_AUTO_CAL[k]
You do not need to recalibrate the tool probe in the AUTOMATIC mode.
Index [k] stands for the number of the actual data field (probe number -1).
Decimal place
ONES 1st axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
TENS 2nd axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
Decimal place
HUNDREDS 3rd axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
Example
If the general cycle machine data SD54632 $SNS_MEA_TP_AX_DIR_AUTO_CAL has the
value 123, the tool probe is calibrated as follows in the G17 plane:
● X in both directions
● Y only in plus direction
● Z only in minus direction
Calibration data of the tool probe referred to the workpiece coordinate system
Before calibration is started, the position of the tool probe in the workpiece coordinate system
(WCS) must be roughly entered into the following general cycle setting data. In this case, the
reference point is the outer diameter or the tool length of the active tool in the spindle. If there
is no tool in the spindle, the reference points are the spindle center point and the tool reference
point at the spindle.
Note
When measuring tools, ensure that the data of the adjustable zero offset or the basic reference
always correspond to the data when calibrating (measuring in WCS!).
Always make measurements and calibrate with the same adjustable zero offset.
Decimal place
ONES 1. Axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
TENS 2. Axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
HUNDREDS 3. Axis
=0 axis not possible
=1 only minus direction
=2 only plus direction
=3 both directions
Example
If the general cycle machine data SD54647 $SNS_MEA_TPW_AX_DIR_AUTO_CAL has the
value 123, the tool probe is calibrated as follows in the G17 plane:
● X in both directions
● Y only in plus direction
● Z only in minus direction
Note
If the spindle is already rotating when the measuring cycle is called, this direction of rotation
remains independent of the setting of this data.
=0 Only single probing with the feedrate calculated by the cycle. However, as a minimum, the
value from SD54673[0] $SNS_MEA_CM_MIN_FEEDRATE.
=≥1 First probing with feedrate. However, as a minimum with the value from
SD54673[0] $SNS_MEA_CM_MIN_FEEDRATE)
SD54675[0] $SNS_MEA_CM_FEEDFACTOR_1
Note
Feedrate factor 2 should be less than feedrate factor 1.
Measurement with rotating spindle: Measured value correction using correction tables
SD54695 to SD54700 Correction values for radius meas‐ See the subsequent general cycle
urement. setting data.
SD54705 to SD54710 Correction values for length meas‐ See the subsequent general cycle
urement. setting data.
Calibration data of the tool probe, referred to the machine coordinate system
Before calibration is started, the position of the tool probe in the machine coordinate system
(MCS) must be entered into the following general cycle setting data.
Note
For a standard lathe with axes X and Z (G18), axis Z is the 1st measuring axis and axis X is
the 2nd measuring axis.
Calibration data of the tool probe referred to the machine coordinate system
If you wish to calibrate the tool probe in the machine coordinate system, then the position of
the tool probe in the machine coordinate system must be entered into the following general
cycle setting data.
Calibration data of the tool probe referred to the workpiece coordinate system
If you wish to calibrate the tool probe in the workpiece coordinate system, then the position of
the tool probe in the workpiece coordinate system must be entered into the following general
cycle setting data. In this case, the reference point is the outer diameter or the tool length of
the active tool in the spindle.
Index [k] stands for the number of the actual data field (probe number -1).
The real angular position of rotary axes can deviate from that programmed (exact stop fine
window) This deviation depends on the position control properties of the axis. The maximum
deviation that can be expected at a specific axis should be entered into the parameter. When
the tolerance is exceeded, Alarm 61442 is output - "Toolholder not parallel to the geometry
axes".
21.10.5 Logging
Increase the value of machine data MD11420 if larger log files have to be stored in the file
system of the NC.
Note
Set MD11422 bit 0 = 1 so that the program runtimes are not lengthened significantly.
References
Operating Manual, Turning/MIlling/Grinding; Chapter "Settings for the measurement result log"
SD55774 $SCS_J_MEA_PROTOCOL_FILE Name and path for the log file for measuring in JOG
//NC:/WKS.DIR/TEMP.WPD/J_MEAPROT.TXT Default setting
Note
The logging operation checks whether the S_USERTXT array is available. If S_USERTXT is
available, the content of the array is logged. If S_USERTXT is not available, the content of the
S_PROTTXT array is logged.
Function
You can make individual adaptations to the log form and content in the CUST_MEAPROT
cycle.
Procedure
1. Open the CUST_MEAPROT.SPF cycle file.
2. Select the program lines in the _MARK1 block.
3. Copy the contents from the _MARK1 block to the _MARK2 block.
4. Adapt the parameters individually in the _MARK2 block.
5. Save the changed cycle file.
The original default values are retained and can be activated/deactivated at any time
(setting of comment characters).
Parameter
In the CUST_MEAPROT cycle, all the possible parameter changes are described in detail in
the _MARK2_1 block.
You can adapt the following parameters:
Precondition
The version details are included in the cycles files in the following form:
;VERSION: <Version> ;DATE: <YYYY-MM-DD>
Example:
;VERSION: 05.05.05.00 ;DATE: 2012-11-30
Procedure
See also
Save information (Page 376)
Logbook (Page 379)
General
You have the possibility to compare a required cycles version with the existing cycles version
in the version view.
File overview
The following files are required:
4. Enter the planned version for the cycles files in the <info> tag with "defaultFileVersion" and
the details for the complete version in the <Version> tag.
5. Close the file to save the changes.
Example:
Standard:
<Component>
<Name>Manufacturer Cycles</Name>
<Path>/siemens/sinumerik/hmi/data/version/oem/cma</Path>
</Component>
Example:
<Component>
<Name>Manufacturer Cycles</Name>
<Path>/oem/sinumerik/hmi/data/version/oem/cma</Path>
</Component>
Additional languages
In addition to the already existing standard languages, additional user interface languages are
available on a separate DVD.
The integrated online help is either displayed in the relevant language of the country or in
English.
Refer to the following chapter for the languages that are available for the user interface:
Supported languages (Page 612)
Precondition
Software option
You require the following software option in order to use this function:
"Additional languages"
● After the installation, approx. 256 MB memory must be available on the CompactFlash Card.
● Language extension software "hmi_sl_language_xxx_02.06.00.00.00y.arc".
xxx = language code, y = internal version ID
Is supplied on the language extension DVD.
Installing a language
Install the language the same as for a commissioning archive (ARC). For the procedure, please
refer to the following Chapter: Reading-in a start-up archive (Page 302)
Note
Additional software language of the previous version is compatible to the actual operating
software.
Note
Standard languages and the currently active language for the operating software cannot be
uninstalled.
Procedure
"systemconfiguration.ini" file
In order to integrate an OEMFrame application into the operating software, copy the
"systemconfiguration.ini" configuration file and place it in one of the two directories:
<Installation path>/user/sinumerik/hmi/cfg
<Installation path>/oem/sinumerik/hmi/cfg
All of the processes to be managed by the system manager, as well as the applications that
are to be integrated as OEMFrame applications are in the [processes] section.
Value Meaning
process Symbolic name of the OEMFrame application. This is required to configure the
operating areas.
cmdline Command line which is transferred to the "oemframe.exe" process when starting.
oemframe For OEMFrame applications, always set to "true".
windowname Window name of the OEMFrame application - should be determined with "find‐
window.exe" or "spy++.exe".
classname Class name of the OEMFrame application - should be determined with "findwind‐
ow.exe" or "spy++.exe".
deferred true: OEMFrame application is not started when SINUMERIK Operate powers up,
but only when selected for the first time.
Example
In the following example, the two Windows applications "notepad.exe" and "calc.exe" are
configured as OEMFrame applications.
[processes]
PROC600= process:=notepadOEM,cmdline:="notepad.exe mytext1.txt",
oemframe:=true, deferred:=true, windowname:="mytext1.txt - Notepad",
classname:="Notepad"
PROC601= process:=calcOEM, cmdline:="calc.exe" oemframe:=true,
windowname:="calculator"
Section [areas]
The SINUMERIK Operate operating areas are configured in this section.
Value Meaning
name Symbolic name for the operating area.
process Name of the OEMFrame application according to section [processes].
Note
Permissible number range
In the "processes" and "areas" sections, the number range 500-999 is reserved for OEM
customers. If you use numbers less than 500, then it is possible that Siemens basis
components will be overwritten!
Example
[areas]
AREA600= name:=AreaOEM, process:=notepadOEM
AREA601= name:=AreaCalc, process:=calcOEM
Note
Only OEMFrame applications are supported that do not use any of the programming interfaces
of SINUMERIK Operate.
Section [miscellaneous]
You can make various settings in this section. Generally, only the start operating area is
changed.
Key Value
startuparea Name of the start operating area
Example
[miscellaneous]
startuparea = AreaOEM
"slamconfig.ini" file
In the "slamconfig.ini" configuration file, for every operating area, you can create a section that
was configured in the "systemconfiguration.ini" file. The section must bear the configured name
of the appropriate operating area, e.g. AreaOEM.
Value Meaning
TextId Text ID for a foreign-language text which will be displayed as the softkey label.
TextContext Context of the foreign-language text.
TextFile Name of the text file which includes the context and the foreign-language text.
Graphic Name of an image file which will be used as an icon for the softkey.
SoftkeyPosition Fixed softkey position of the area softkey. In this case, softkey positions 1 to 8 are
located on the 1st horizontal bar and softkey positions 9 to 16 on the 2nd horizontal
bar, etc.
AccessLevel Access level from which the softkey will be displayed. If this value is not specified,
the access level 7 (keyswitch position 0) is set.
Example
The softkey for the "AreaOEM" operating area with the following properties is configured in
the following example:
● The softkey displays the text which has been stored in the "mytext_<lng>.ts" text file under
the context "mycontext" with the "MY_AREA" TextID.
● The "mypicture.png" icon is displayed on the softkey.
● The softkey is located at position 7 in the operating area menu.
● The softkey with access level 5 (keyswitch position 2) is displayed.
[AreaOEM]
; Text-ID of a language dependent text
TextId = MY_AREA
; File name of the text file which contains the Text-ID
TextFile = mytext
; Context in the text file to which the Text-ID is assigned to
TextContext = mycontext
; File name of an icon shown on the area softkey
Picture = mypicture.png
; Position of the area softkey on area menu,
; If no position is specified, an empty position is searched
SoftkeyPosition = 7
; Access level of the area softkey
AccessLevel = 5
Note
Operating area position 7 is reserved for OEM customers.
Attribute Description
context Context within the text file.
Each file must have at least one context.
name Name of the context.
Attribute Description
message Text translation.
There must be at least one message per context.
source Text identifier.
translation Translated text.
remark Text comment (optional).
chars Maximum possible length of the text in characters. If nothing is specified, the
text can have any length (optional).
lines Maximum number of lines available for display. If nothing is specified, the
number of lines is unlimited (optional).
Structure of the language-dependent ts file that contains the labeling text for the softkey:
mytext_<lng>.ts
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<!DOCTYPE TS>
<TS>
<context>
<name>mycontext</name>
<message>
<source>MY_AREA</source>
<translation>Text, which is displayed on the softkey</translation>
<remark>Remark (optional)</remark>
<chars>20</chars>
<lines>2</lines>
</message>
</context>
</TS>
General Information
If you install SINUMERIK Operate using PC/PCU, then the execution is realized using an MSI
setup. The following installation versions are available, which you can use in the interactive or
silent mode using the appropriate Windows command line:
● SINUMERIK Operate complete installation
● SINUMERIK Operate base installation with auxiliary files
● SINUMERIK Operate base installation without auxiliary files
Execution
You control setup execution using command line arguments. The interactive mode /v allows
you to transfer parameter strings to setup.exe. If you wish to run setup without user interaction,
then you can extend the parameter string with the silent mode /qn.
Place the parameter string in inverted commas. If you use several parameters in the string,
separate these using spaces.
If you do not specify any arguments when calling setup.exe, then the complete installation is
run in the interactive mode.
Note
Do not put any spaces between /v and the parameter string.
Note
If you want a progress display in the silent mode, then instead of specifying /qn you can also
specify /qb!.
Installation path
If you install the PC version of SINUMERIK Operate, then you can additionally specify the
installation path:
setup.exe /s /v"/qn INSTALLDIR=C:\Programme\testdir"
For spaces in the path:
setup.exe /s /v"/qn INSTALLDIR=\"C:\Program Files\testdir\""
Exit code
You can identify a successful installation or errors based on the exit code of the setup.exe call:
Log file
During the installation you can generate a log file with /L:
setup.exe /s /v"/qb! /L*vx log.txt"
Procedure
Procedure
File Meaning
"sljkconfig.ini" configuration file File in which the traversing keys are configured.
Text file "oem_sljk_xxx.ts" File for labeling traversing keys in a foreign language, xxx =
language code
Entries Meaning
[State_1] Labeling type - changed via the PLC.
ParamText_x_y Text of the traversing key that is made up of parameters.
Two-line labeling is possible, whereby max. five characters are possible per line.
x: Specifies the position of the key within the row (2 to 7).
y: Specifies the key row (1 or 2).
%m1 The machine axis name of the first axis is referenced and displayed as
text. The current active axis number is read out from data block DB10.
The name from the machine data is determined via this index.
%n Defines the position in the text for the line break.
%a1 The alias axis name of the first axis is referenced and displayed as text.
The current active axis number is read out from data block DB10. The
name from the "oem_sljk_eng.ts" text file is determined via this index.
Entries Meaning
TextId_x_y Text of the traversing key that is read from the text file (target language text).
Picture_x_y File name of the icon to be displayed.
The files with the icons must be located in the following directories: /oem/sinumerik/
hmi/ico and
depending on the resolution of the subdirectories:
/ico640
/ico800
/ico1024
/ico1280
Procedure
1. Copy the "sljkconfig.ini" configuration file from the folder
/siemens/sinumerik/hmi/template/cfg
2. Place the copy into the folder /oem/sinumerik/hmi/cfg
or /user/sinumerik/hmi/cfg
3. Open the copy in the Editor and define the traversing key labeling.
[State_1]
TextId_1_1 = OEM_JK_TEXT_1
TextId_1_2 = OEM_JK_TEXT_2
ParamText_2_1 = %a1%n-
ParamText_2_2 = %a1%n+
ParamText_3_1 = %a2%n-
ParamText_3_2 = %a2%n+
ParamText_4_1 = %a3%n-
ParamText_4_2 = %a3%n+
ParamText_5_1 = %a4%n-
ParamText_5_2 = %a4%n+
ParamText_6_1 = %a5%n-
ParamText_6_2 = %a5%n+
ParamText_7_1 = %a6%n-
ParamText_7_2 = %a6%n+
Picture_8_1 = AlarmCancel.png
Picture_8_2 = AlarmNCReset.png
Entries Meaning
name Freely selectable name of the text context.
In the text file template, the name of the text context is "SIJkLabels" and stands for the
traversing key labeling (solution line jog key labels). This identifier is already stored in
the configuration file.
source Traversing key identifier of the respective axis. This text ID is referenced in the "sljkcon‐
fig.ini" configuration file with the "TextId_2_1".
The text IDs for the alias names (JK_AXISNAME_2 to JK_AXISNAME_7) must not be
changed.
translation Input of the foreign language text for the axis specified in <source>.
Procedure
1. You can copy the sample file " oem_sljk_deu.ts" from the following directory: /siemens/
sinumerik/hmi/template/lng.
2. Store or create the file in the /oem/sinumerik/hmi/lng or
/user/sinumerik/hmi/lng directory.
3. Give the file a name, e.g. for German texts: "sljk_deu.ts".
If you wish to set-up the labeling for additional languages, a separate file must be created
for each language. Save the file with the appropriate language code in the file name. To
do this, use the language codes specified above.
4. Open the file and in the <message> and </message> area, define the labeling.
5. Restart the HMI.
In order that the labeling is displayed during the program runtime, the file must be converted
into a binary format. This conversion is only executed when the HMI powers up.
<message>
<source>JK_AXISNAME_8</source>
<translation>V</translation>
</message>
<message>
<source>JK_AXISNAME_9</source>
<translation>W</translation>
</message>
<message>
<source>JK_AXISNAME_10</source>
<translation>UV1</translation>
</message>
<message>
<source>JK_AXISNAME_11</source>
<translation>UV2</translation>
</message>
<message>
<source>JK_AXISNAME_12</source>
<translation>UV3</translation>
</message>
<!-- User defined language dependent text (example) -->
<message>
<source>OEM_JK_TEXT_1</source>
<translation>SF1</translation>
</message>
<message>
<source>OEM_JK_TEXT_2</source>
<translation>SF2</translation>
</message>
</TS>
See also
Supported languages (Page 612)
Note
If you wish to create or edit the file on a PC, use an editor that supports UTF-8 coding.
Tag Meaning
source Designation for the user softkey. "SK_USERKEY1" to "SK_USERKEY16" are possi‐
ble, whereby the names may not be changed.
comment User-specific description of the key assignment.
translation Text that should be shown on the key.
● A maximum of 10 characters are possible per line.
● 2-line labeling is possible, whereby the line break is set using "%n".
remark Remark for key assignment.
chars Number of characters. A maximum of 10 characters per line are possible.
lines Number of lines. 2 lines are possible.
Procedure
1. You can copy the sample file " oem_slck_deu.ts" from the following directory: /siemens/
sinumerik/hmi/template/lng.
2. Store or create the file in the /oem/sinumerik/hmi/lng or
/user/sinumerik/hmi/lng directory.
3. Give the file a name, e.g. for German texts: "slck_deu.ts".
If you wish to create the key labeling for additional languages, then a separate file must be
created for each language. Save the file with the appropriate language code in the file name.
To do this, use the language codes specified above.
4. Open the file and in the <message> and </message> area, define the key labeling.
5. Restart the HMI.
In order that the key labeling is displayed during the program runtime, the file must be
converted into a binary format. This conversion is only executed when the HMI powers up.
<!DOCTYPE TS><TS>
<context>
<name>SlCkDialog</name
<message>
<source>SK_USERKEY1</source>
<comment></comment>
<translation>U1</translation>
<remark>User key 1</remark>
<chars>10</chars>
<lines>2</lines>
<languageIndependent>true</languageIndependent>
</message>
<message>
<source>SK_USERKEY2</source>
<comment></comment>
<translation>U2</translation>
<remark>User key 2</remark>
<chars>10</chars>
<lines>2</lines>
<languageIndependent>true</languageIndependent>
</message>
<message>
.....
</message>
</context>
</TS>
See also
Range of alarms (Page 244)
Function
Active functions can be displayed at the configurable user keys via the PLC. For instance,
small LEDs can be emulated on the softkeys.
You configure the function in the "slckcpf.ini" file.
Interface signals
The PLC bits are in the output image of the PLC-HT 8 interface and are analog to those in the
input image.
Section Description
UserKeyLEDIcon Name of the icon file.
Standard entry: led_green.png
OFF Deactivates the icon display.
PRESSED Displays the active functions by pressing
down the softkey.
UserKeyLEDIconAlignment Specifies the position of the icon.
Standard position: AlignLeft | AlignTop
Horizontal and vertical alignments can be combined. The two
names are separated by the "|" character.
The following alignments are possible:
AlignLeft Left
AlignRight Right
AlignHCenter Horizontal, center
AlignTop Top
AlignBottom Bottom
AlignVCenter Vertical, center
UserKeyLEDMap Specifies the start address of the output image.
Entries can be made in the following form: "DBx.DBBy", "ABx",
"MBx".
Default setting: The start address is determined using
DB7 MCP1Out (or MCP2Out).
Section Description
U1LED ... U16LED The status bit address can be defined - different from the output
VarIncLED image - using these entries.
SBLLED Note: The offsets from the HT 8 output image, for one or several
softkeys, are not taken into consideration.
WCSLED
showVarIncLED true When the increment mode is active, the icon is also
displayed on the "[VAR]" softkey.
false The icon is not displayed.
showSBLLED true When the SingleBlock mode is active, then the icon
is also displayed on the "Single Block" softkey.
false The icon is not displayed.
showWCSLED true When the SingleBlock mode is active, then the icon
is also displayed on the "Single Block" softkey.
false The icon is not displayed.
1. You can copy the sample file "slckcpf.ini" from the following directory: /siemens/sinumerik/
hmi/template/cfg
2. Store the file in the /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg directory.
3. If you use your own icon, then locate it together with the corresponding resolution for HT 8
directory: /oem/sinumerik/hmi/ico/ico640 or /user/sinumerik/hmi/ico/ico640.
4. Open the file and make the appropriate settings.
; Use the following settings to use this status bits instead of the
led map for a specific sk
;U1LED=/channel/parameter/R[U1,1]
;....
;U16LED=/channel/parameter/R[U1,16]
;VarIncLED = DB11.DBX8.5
;SBLLED = DB21.DBX0.4
;WCSLED = DB19.DBX0.7
Abbreviation Meaning
MLFB Maschinenlesbare Fabrikatbezeichnung
MPF Main Program File: NC part program (main program)
MCP Machine Control Panel: Machine control panel
NC Numerical Control: Numerical control
NCK Numerical Control Kernel: NC kernel with block preparation, traversing range, etc.
NCU Numerical Control Unit: NCK hardware unit
NFS Network File System
NTP Network Time Protocol
ZO Zero offset
OEM Original Equipment Manufacturer
OID Object Identifier: Information identifier
OP Operator Panel
PCU Programmable Control Unit
PI service Program Invocation Services
PG Programming device
PLC Programmable Logic Control
RFC Request for Comments
REF REFerence point approach function
REPOS REPOSition function
ROV Rapid Override: Input correction
RPA R-Parameter Active: Memory area in NCK for R- NCK for R parameter numbers
SBL Single Block: Single block
SD Setting Data
SDB System Data Block
SEA Setting Data Active: Identifier (file type) for setting data
SK Softkey
SMB Server Message Block
SNMP Simple Network Management Protocol
SPF Sub Program File: Subroutines
SRAM Static Random Access Memory: Static RAM (non-volatile)
SSH Secure Shell: Network protocol
SW Software
SYF System Files: System files
TCU Thin Client Unit
TEA Testing Data Active: Identifier for machine data
TMA Tool Magazine Active: Magazine data
TO Tool Offset: Tool offset
TOA Tool Offset Active: Identifier (file type) for tool offsets
UDP User Datagram Protocol: Network protocol
UFR User frame
VNC Virtual Network Computing
FD Feed Drive
Abbreviation Meaning
WCS Workpiece Coordinate System
TM Tool Management
Direction of rotation
Counterspindle, 497
Main spindle, 491 F
Directory structure, 19
Face machining
Display filter
in turning, 508
Machine data, 72
under ShopTurn, 511
Display groups, 73
Fail-safe I/O modules, 459
Display machine data, 68
fast block search, 96
Search, 76
File
Displaying AS-i, 424
Copy, 22
Drilling, 470
Copying with WinSCP, 25
Drive
Cut, 23
Execution from External Storage, 53
Delete, 23
Global part program memory, 53
Displaying in preview window, 24
Logical drive, 51
External editing, 24
Set EXTCALL, 52
insert, 22
Setting up, 51
Open, 22
Drive parameters
Protection area elements, 284
Display/change, 70
Renaming, 23
for machine data, 65
Form-truing, 516
Drive system
Frame
Diagnostics, 393
Protection area element, 278
Diagnostics - details, 394
Drive-specific machine data, 65
G
E G code groups
Configuring the display, 88
Editing an xml file, 24
G group 59, 571
Editing enum values, 75
G-code program, 213
Editing the tool and magazine management, 214
General machine data, 65
Engraving, 481
General setting data, 68
Entering BICO values, 75
Generating a crashlog file, 383
Error analysis, 328
Generating an archive for the Hotline, 307
Error file of the alarms, 246
Grinding parameters
Ethernet/PROFINET
Identifiers, 157
Diagnostics, 340
Displaying messages, 341
Network trace, 342
Trace parameters, 343
H
EUNA, 370 Hardware components
EXIT, 622 Adding, 378
Displaying the softkey, 32 Entering, 377
Expert parameters, 73 HEAD_1, 537
EXTCALL High-Speed Settings, 569
switch off and on again, 52 Hirth joint, 522, 564
Extended reset, 71 HMI PRO RT, 420
HMI restart
Displaying the softkey, 32
HMI trace, 389
HOLES2, 481
HT 8
Activating, deactivating the virtual keyboard, 31
ShopMill PCU, 17
Settings for milling, 482 under Windows, 17
Tool-specific functions, 187 Start-up archive
ShopTurn Creating, 300
Cylinder surface transformation, 507 Reading in, 303
Face machining, 511 Station-related network diagnostics, 325
Inclined Y axis, 512 Status display
Setting up a counterspindle, 496 Inserting a logo, 87
Settings for turning, 491 Status display with icons, 100
Simulation STO Safe Torque Off, 458
Cycle application, 474 Stock removal, corner, 500
Deactivate, 108 Surface grinding, 516
General conditions, 105 Displaying softkeys, 466
Grinding technology, 107 Switch
Milling technology, 107 Kinematic elements, 273
Turning technology, 107 Swiveling
Simultaneous recording, 109 activate, 518
Activating the machining time, 110 Configuring input screens, 518
Option, 109 Creating angled tools, 520
slaesvcadapconf.xml, 229, 231, 234, 241, 257 Declare data sets, 520
slaesvcconf.xml, 235, 243 Example HEAD_2, 539
slckcpf.ini, 631 Example MIXED_45, 542
slhlp.xml, 433 Example TABLE_45, 540
slmagcodeconfig.ini, 88 Example TABLE_5, 544
SLOT2, 481 Offset vectors, 529
sltlprodiaghmi.ini, 422, 423 Retraction, 536
Softkey Rotary axes, 533
Access level, 39 Set up kinematic chain, 526
Original setting, 40 System utilization, 368
Source ID, 245
Source URL, 245
Specify the IP address of the NCU, 621 T
Sphere
Tailstock
Protection area elements, 281
Option, 109
Spindle analog, 116
Tapping, 472
Spindle control, 115
TEACH IN, 94
Spindle diagnostics, 118
Technology
Additional temperature sensor, 123
Cylindrical grinding, 516
Clamping state, 125
Drilling, 470
Clamping time statistics, 128
Milling, 480
Diagnostic statistics, 127
Surface grinding, 516
Logistics data, 128
Swiveling, 517
Motor temperature sensor, 122
Turning, 500
Speed limitation, 126
Template files, 22
Spindle load, 124
Test license, 46
Temperature, 120
TextPad, 18
Temperature histograms, 123
Thread-cutting, 500
SS1 Safe Stop 1, 458
Time
Standard parameter specifications of alarm
Selecting the format, 29
texts, 245
Setting, 29
Starting SINUMERIK Operate
Time server, 30
NCU, 17
Tool clamping angle, 564
U
USB FlashDrive, 18
USB keyboard, 18
User view
Creating, 81
Delete, 84
Editing, 82
Importing, 80
user.xml, 374
Using angular tools, 520
V
Variable screen forms, 352
W
WinSCP, 18, 25
Workpiece measurement
under milling, 582, 595
under turning, 602
Valid for:
10/2015
6FC5397-1DP40-5BA3
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Introduction...................................................................................................................................................5
2 Setting up OPC UA components..................................................................................................................7
2.1 Requirement.............................................................................................................................7
2.2 Setup........................................................................................................................................8
3 Testing the connection...............................................................................................................................13
4 OPC UA Data Access - functional scope...................................................................................................21
4.1 User administration................................................................................................................22
4.2 Browsing................................................................................................................................26
4.3 Variable paths........................................................................................................................28
4.3.1 Variable paths for NC access operations...............................................................................28
4.3.2 Variable paths for GUD access operations............................................................................29
4.3.3 Variable paths for PLC access operations.............................................................................29
4.3.4 Variable paths for machine and setting data..........................................................................32
4.3.5 Variable paths for 1:N configuration (only target system PCU)..............................................32
4.4 Supported services................................................................................................................34
4.5 Special features with regard to the OPC UA specification.....................................................35
Index...........................................................................................................................................................37
Software option
You require the following software option in order to use this function: SINUMERIK
Integrate for Engineering "Access MyMachine / OPC UA".
Characteristics
Important features include:
● Independent of any particular platform
● Security
● Service call timeouts
● Heartbeat
● Buffering
Logs
Today, two protocols are available for transport via the network:
1. Binary protocol
URL: opc.tcp://ServerTCP-Port 4840
Optimized for
– Low overhead
– Low usage of resources
– Interoperability
2. Web service (SOAP)
URL: http://Server
Ports 80 (http) and 443 (https)
Optimized for
– Tool support (used from "Java" or under ".NET")
– Firewall compatibility
Information is provided in what is known as the "address space". This is comprised of "nodes"
and "references". Detailed information on this is provided on the OPC Foundation (https://
opcfoundation.org/) page.
The binary protocol is supported in the SINUMERIK environment. Currently, OPC UA Data
Access is offered as service.
2.2 Setup
Setting Description
IP address The IPv4 address of the target system. This is determined automatically.
Check these:
for the NCU and PPU -X130
for the PCU 50 Local Area Connection 2
Port TCP port, communicates via the OPC UA. This is added to the firewall
exceptions for NCU and PPU.
(The standard for the OPC UA communication is the TCP port 4840)
Admin User Name of the administrator; with it you can add or delete other users and
assign or delete user authorizations.
Password Password of the administrator.
Activate OPC UA Place the checkmark to activate OPC UA and remove the checkmark to
deactivate it.
Note
If you want to change the administrator password later, you can do this via the OPC UA method
"ChangeMyPassword".
Then choose "OK". If you enter a different port from the standard OPC UA TCP port (4840),
you will receive a safety note.
Note
The certificate needed for secure OPC UA communication (../siemens/sinumerik/hmi/miniweb/
System/Cert/servercerts/MiniWeb_OPCUA.crt) is automatically created during the first run-up.
The start date of the validity period is set to the current date. The validity period is 30 years.
If the time is subsequently changed so that it lies outside the validity period, the secure OPC
UA communication does not function (BadCertificateTimeInvalid).
Performing a restart
Perform a hardware restart on the target systems NCU and PPU. A restart of the
SINUMERIK Operate is necessary on the PCU 50.
Note
There are two ways to establish the connection:
● Connection without security
● Connection with the security policy "Basic128Rsa15" and the security mode
"SignAndEncrypt"
Installation
The "Sample Applications" additionally install a service with the name "OPC UA Local
Discovery Server". Should you want to locally test the OPC UA connection, i.e. an installation
directly on the PCU 50, you must deactivate this service.
Note
If the service "OPC UA Local Discovery Server" is active, the SINUMERIK OPC UA server
cannot be started correctly, because it blocks the needed TCP port 4840.
The service has no influence if the "Sample Applications" are installed on a PC in the network.
Deactivation is then not necessary.
Figure 3-1 Deactivating the "OPC UA Local Discovery Server" service on PCU 50
Procedure
1. Start the OPC UA "Sample client".
3. Now enter the IPv4 address of the target system and click the "Discover" button.
4. The SINUMERIK OPC UA server appears in the list. Select the server and confirm with
"OK".
5. Return to the main window and click the "Connect" button.
6. To establish a simple connection without security, make the following settings. Enter the
administrator user assigned when OPC UA was set up and his password by pressing "..."
for "User Identity". Then confirm the settings with "OK".
7. Make the following settings in the "Open Session" dialog. It is necessary to enter the
administrator user and the assigned password again here. Confirm with "OK".
Confirm the prompt asking if you want to trust the transferred certificate with "Yes".
The connection to the SINUMERIK OPC UA server has now been established and the
available address space is displayed.
8. Now navigate to a nodeID (e.g. R-parameter at Sinumerik > Channel > Parameter > R) and
right-click the corresponding entry. You can now test various functions:
Figure 3-8 NodeID "Sinumerik > Channel > Parameter > R"
– The attributes of a NodeID can be queried via the entry "View Attributes". One of these
attributes is the "Value", which provides the corresponding value of R1.
Note
The communication time is not guaranteed. As a consequence, realtime tasks cannot be
implemented using the OPC UA data access interface.
Detailed information on the OPC UA specification is provided on the OPC Foundation (https://
opcfoundation.org/) page.
Using the OPC UA data access interface, data can be accessed on the NC and PLC. In
particular, variables can be read and written, and you can be notified when a value changes.
You can access individual variables (e.g. /Channel/Parameter/R[u1,1]) and array variables
(e.g. /Channel/Parameter/R[u1,1,10]).
Note
Limited number of simultaneously monitored variables
The number of variables from the "Sinumerik" object that can be monitored simultaneously is
limited:
● SINUMERIK 828D, maximum 100 variables
● SINUMERIK 840D sl, maximum 200 variables
If you attempt to monitor more variables, the "BadNodeIdUnknown" error is returned.
User administration
To establish a connection to the OPC UA Data Access interface, an authentication with user
name and password is required.
Note
Anonymous connection
You can also establish an anonymous connection, but none of the functions will be available
(feedback: "BadInternalError").
For an initial connection, you must use the administrator user and password assigned when
OPC UA was set up. Methods with the following functions will then be available under the node
"Sinumerik/Methods":
● Add own users
● Delete own users
● Assign rights
● Remove rights
Note
You can only add/remove users/rights if you are connected as administrator. If you call the
methods with a different user, you will receive the message "BadInvalidArgument".
Method Description
AddUser Creates a new user for accessing OPC UA.
Input Arguments:
UserName User Name
Initially, the password of the new user corresponds to the user name. It should
then be changed using the method "ChangeMyPassword".
DeleteUser Deletes a user who was added previously using the method "AddUser".
Input Arguments:
UserName User Name
The administrator user created when OPC UA was set up cannot be deleted.
Method Description
ChangeMyPassword Changes the password for the connected user.
Input Arguments:
OldPwd Current password
NewPwd1 New password
NewPwd2 New password (security prompt)
Important!
Whereas the methods "AddUser", "DeleteUser", "GiveUserAccess" and "De‐
leteUserAccess" can only be called up if the user is connected as the admin‐
istrator, the user must connect as the corresponding user in order to change
the password.
Method Description
GiveUserAccess Sets the specified access rights for a user. The rights below can be combined
in any combination.
Input Arguments:
User User name which is to given the rights
Realm The access rights to be set as a string.
If a user wants to set several rights,
they must be separated by a semico‐
lon.
Some possible realm strings are:
"StateRead" Status data - NC, channel, axis, read
access
"StateWrite" Status data - NC, channel, axis, write
access
"FrameRead" Zero offsets, read access
"FrameWrite" Zero offsets, write access
"SeaRead" Setting data, read access
"SeaWrite" Setting data, write access
"TeaRead" Machine data, read access
"TeaWrite" Machine data, write access
"ToolRead" Tool and magazine data, read access
"ToolWrite" Tool and magazine data, write access
"DriveRead" Drive data, read access
"DriveWrite" Drive data, write access
"GudRead" User data, read access
"GudWrite" User data, write access
"PlcRead" PLC, read access
"PlcWrite" PLC, write access
"RandomRead" Random (and ReadVar method), read
access
"RandomWrite" Random (and WriteVar method), write
access
"SinuReadAll" All of the read access operations men‐
tioned
"SinuWriteAll" All of the write access operations men‐
tioned
Example:
GiveUserAccess("MyUser", "GudRead; PlcWrite")
Sets the read access for user data for the "MyUser" user and sets the write
access for the PLC.
Method Description
DeleteUserAccess Deletes the specified access rights for a user.
Input Arguments:
User A user whose rights are to be deleted
Realm The access rights to be deleted as a
string.
If a user wants to delete several rights,
they must be separated by a semico‐
lon.
For possible realm strings, see "GiveUserAccess".
4.2 Browsing
If the OPC UA data access interface is browsed, then the available address space is mapped
under "Sinumerik".
Global User Data (GUD) can be found under the "/Sinumerik/GUD" node.
The PLC blocks (inputs, outputs, bit memory, data blocks) can be found under the "/Sinumerik/
Plc" node.
Machine data can be found under the node "/Sinumerik/TEA".
Setting data can be found under the node "/Sinumerik/SEA".
Observe the following during browsing:
● In the address space of the NC, the displayed variables always represent only the first
parameter of the corresponding first OPI unit.
Example:
The R parameters can be found under "Sinumerik > Channel > Parameter > R". The
corresponding identifier is called "/Channel/Parameter/R", which is finally mapped to "/
Channel/Parameter/R[u1, 1]". If you want to access other parameters, then you must
correspondingly extend the identifier; you cannot directly accept the identifiers obtained
when browsing, e.g. "/Channel/Parameter/R[u2, 56]".
● In the address space of the NC, the displayed variables represent the access format that
has to be extended accordingly.
Example:
The variable "/Plc/MB" is in the address space. This variable must be extended by the
appropriate byte number, e.g. "/Plc/MB6". Only then is a value supplied.
● The address space of the NC also contains variables that are not available in a
corresponding machine configuration. These variables return "BadAttributeIdInvalid" as
value.
Figure 4-1 Excerpt from browsing the OPC UA data access interface
The displayed NC variables always represent only the first parameter of the corresponding
NC data area (channel, TO area, mode group).
Example
The R parameters are found under the identifier "/Channel/Parameter/R", which is eventually
mapped to "/Channel/Parameter/R[u1, 1]". If you want to access other parameters, then you
must correspondingly extend the identifier, e.g. "/Channel/Parameter/R[u2, 56]".
ARRAY[0] → /NC/_N_NC_GD3_ACX/ARRAY[1]
ARRAY[1] → /NC/_N_NC_GD3_ACX/ARRAY[2]
ABC[0,0] → /NC/_N_CH_GD3_ACX/ABC[u1, 1]
ABC[0.1] → /NC/_N_CH_GD3_ACX/ABC[u1, 2]
ABC[0.2] → /NC/_N_CH_GD3_ACX/ABC[u1, 3]
ABC[1.0] → /NC/_N_CH_GD3_ACX/ABC[u1, 4]
ABC[1.1] → /NC/_N_CH_GD3_ACX/ABC[u1, 5]
ABC[1.2] → /NC/_N_CH_GD3_ACX/ABC[u1, 6]
ABC[2.0] → /NC/_N_CH_GD3_ACX/ABC[u1, 7]
ABC[2.1] → /NC/_N_CH_GD3_ACX/ABC[u1, 8]
ABC[2.2] → /NC/_N_CH_GD3_ACX/ABC[u1, 9]
In the address space of the NC, the displayed variables represent the access format that has
to be extended accordingly.
Example
The variable "/Plc/MB" is in the address space. This variable must be extended by the
appropriate byte number, e.g. to "/Plc/MB6". Only then is a value supplied.
Access formats
The various access formats are shown in the following table. When the default data type (bold
format) is used, you must expand it by the prefix "/Plc". For all others, it must be expanded by
the prefix "/Random/Plc".
Note
The data type is converted during access with the OPC UA data access interface. Refer to the
following table for the data type conversions.
Note
● Timers can only be read. A timer is active if it contains a value other than 0.
● If the data type CHAR or STRING is used in conjunction with a byte access, UTF8
characters are read, but if either data type is used in conjunction with a word access, UTF16
characters are read.
● Variables of the STRING type contain the maximum length in the first byte and the actual
length in the second byte. When strings are written, the actual length is adapted accordingly.
The maximum length is not changed.
● For the STRING data type in conjunction with a byte access (e.g. "/Plc/
DB99.DBB0:STRING"), the maximum string length is 255 characters. As a result of the
UTF8 formatting, for some characters (e.g. for the "µ"), two bytes are required, so that the
maximum string length is correspondingly reduced.
● Only one-dimensional arrays are supported. With STRING arrays, all elements have the
same maximum length.
4.3.5 Variable paths for 1:N configuration (only target system PCU)
By default, data is accessed on the NCU which is being viewed by SINUMERIK Operate.
Switching to a different NCU in the SINUMERIK Operate results in a situation where the
SINUMERIK OPC UA server is also looking at the value of the now active NCU.
If the access is to be to a specific NCU, the NodeId must be expanded with a prefix:
/Random@<NCUName><NodeId>
Note
The NCU names are listed in the "MMC.ini" file.
Entry:
[GLOBAL]
NcddeMachineNames=NCU1,NCU2
TranslateBrowsePathsToNodeIdsService
If a non-existing NodeId is specified in TranslateBrowsePathsToNodeIds, then "BadNoMatch"
is returned instead of "BadNodeIdUnknown".
ArrayDimensions
The attribute "ArrayDimensions" is not supported and always gives "BadAttributeIdInvalid".
Return values
At places where a "BadNodeIdInvalid" is expected, a "BadAttributeIdInvalid" can also be given.
MaxNotificationsPerPublish
The property "MaxNotificationsPerPublish" is not evaluated.
IndexRange
Reading with "IndexRange" is not supported.
ServerDiagnostics
DiagnosticInfos are not supported.
B
Binary protocol, 5
Browsing, 26
C
ChangeMyPassword, 23
Characteristics, 5
Checking the time, 11
Configuration dialog, 9
D
Data types, 30
DeleteUser, 22
DeleteUserAccess, 25
G
GiveUserAccess, 24
L
License, 8
Logs, 5
O
OPC UA data access interface
Functional scope, 21
OPC UA Local Discovery Server, 13
V
Variable monitoring
Maximum number, 21
Variable paths, 28
Getting Started 2
Fundamentals 3
SINUMERIK
Dialogs 4
SINUMERIK 840D sl/828D
SINUMERIK Integrate Run 5
Variables
MyScreens (BE2)
Programming commands 6
Programming Manual
Dialog selection 9
Reference lists A
Animated elements C
Valid for:
10/2015
6FC5397-1DP40-5BA3
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Introduction...................................................................................................................................................9
2 Getting Started...........................................................................................................................................13
2.1 Introduction............................................................................................................................13
2.2 Example.................................................................................................................................13
2.2.1 Task description.....................................................................................................................13
2.2.2 Creating the configuration file................................................................................................17
2.2.3 Saving the configuration file in the OEM directory.................................................................20
2.2.4 Creating the online help.........................................................................................................21
2.2.5 Saving the online help in the OEM directory..........................................................................23
2.2.6 Copying easyscreen.ini into the OEM directory.....................................................................23
2.2.7 Registering the COM file in easyscreen.ini............................................................................24
2.2.8 Testing the project..................................................................................................................24
3 Fundamentals.............................................................................................................................................25
3.1 Structure of configuration file.................................................................................................25
3.2 Structure of the menu tree.....................................................................................................27
3.3 Definition and functions for start softkeys..............................................................................28
3.3.1 Defining the start softkey........................................................................................................28
3.3.2 Functions for start softkeys....................................................................................................29
3.4 Troubleshooting (log book)....................................................................................................31
3.5 Notes on the easyscreen.ini...................................................................................................32
3.6 Notes for personnel changing over to "Run MyScreens".......................................................34
3.7 Extended configuration syntax...............................................................................................36
3.8 SmartOperation and MultiTouch operation............................................................................37
4 Dialogs........................................................................................................................................................39
4.1 Structure and elements of a dialog........................................................................................39
4.1.1 Defining a dialog....................................................................................................................39
4.1.2 Defining dialog properties......................................................................................................41
4.1.3 Defining dialog elements........................................................................................................47
4.1.4 Defining dialogs with multiple columns..................................................................................48
4.1.5 Password dialogs...................................................................................................................50
4.1.6 Using display images/graphics...............................................................................................52
4.2 Defining softkey menus..........................................................................................................52
4.2.1 Changing softkey properties during runtime..........................................................................55
4.2.2 Language-dependent text......................................................................................................58
4.3 Configuring the online help....................................................................................................61
5 Variables.....................................................................................................................................................63
5.1 Defining variables...................................................................................................................63
6.2.6 LANGUAGE.........................................................................................................................104
6.2.7 LOAD...................................................................................................................................104
6.2.8 UNLOAD..............................................................................................................................105
6.2.9 OUTPUT..............................................................................................................................106
6.2.10 PRESS.................................................................................................................................107
6.2.11 PRESS(ENTER)..................................................................................................................108
6.2.12 PRESS(TOGGLE)................................................................................................................108
6.2.13 RESOLUTION......................................................................................................................109
6.2.14 RESUME..............................................................................................................................109
6.2.15 SUSPEND............................................................................................................................110
6.2.16 Example: Version management with OUTPUT methods.....................................................110
6.3 Functions..............................................................................................................................112
6.3.1 Reading and writing drive parameters: RDOP, WDOP, MRDOP........................................112
6.3.2 Subprogram call (CALL).......................................................................................................114
6.3.3 Define block (//B)..................................................................................................................115
6.3.4 Check Variable (CVAR).......................................................................................................116
6.3.5 CLEAR_BACKGROUND......................................................................................................117
6.3.6 Copy Program file function (CP)..........................................................................................118
6.3.7 Delete Program file function (DP)........................................................................................118
6.3.8 Exist Program file function (EP)...........................................................................................119
6.3.9 Move Program file function (MP)..........................................................................................120
6.3.10 Select Program file function (SP).........................................................................................121
6.3.11 File accesses: RDFILE, WRFILE, RDLINEFILE, WRLINEFILE...........................................122
6.3.12 Dialog line (DLGL)................................................................................................................124
6.3.13 DEBUG................................................................................................................................125
6.3.14 Exit dialog (EXIT).................................................................................................................126
6.3.15 Dynamic manipulation of the lists of toggle fields or list box fields.......................................127
6.3.16 Evaluate (EVAL)...................................................................................................................130
6.3.17 Exit Loading Softkey (EXITLS).............................................................................................131
6.3.18 Function (FCT).....................................................................................................................131
6.3.19 Generate code (GC).............................................................................................................133
6.3.20 Password functions..............................................................................................................136
6.3.21 Load Array (LA)....................................................................................................................137
6.3.22 Load Block (LB)....................................................................................................................138
6.3.23 Load Mask (LM)...................................................................................................................139
6.3.24 Load Softkey (LS)................................................................................................................140
6.3.25 Load Grid (LG).....................................................................................................................141
6.3.26 Multiple selection SWITCH..................................................................................................142
6.3.27 Multiple Read NC PLC (MRNP)...........................................................................................143
6.3.28 PI services............................................................................................................................145
6.3.29 Reading (RNP) and writing (WNP) system or user variables...............................................146
6.3.30 RESIZE_VAR_IO and RESIZE_VAR_TXT...........................................................................147
6.3.31 Register (REG).....................................................................................................................148
6.3.32 RETURN..............................................................................................................................149
6.3.33 Recompile............................................................................................................................150
6.3.34 Recompile without user comment........................................................................................151
6.3.35 Search Forward, Search Backward (SF, SB).......................................................................154
6.3.36 STRING functions................................................................................................................155
6.3.37 WHILE/UNTIL loops.............................................................................................................161
6.3.38 Cyclic execution of scripts: START_TIMER, STOP_TIMER................................................164
Basic configuration
The "Run MyScreens" function enables machine manufacturers to configure their own dialogs.
Even with the basic configuration, it is possible to configure five dialogs in the operator menu
tree or for customer-specific cycle dialogs.
Software option
To expand the number of dialogs, you require one of the following software options:
● SINUMERIK 828D/840D sl, SINUMERIK Integrate Run MyScreens
(6FC5800-0AP64-0YB0)
● SINUMERIK 840D sl, SINUMERIK Integrate Run MyScreens + Run MyHMI
(6FC5800-0AP65-0YB0)
● SINUMERIK 840D sl, SINUMERIK Integrate Run MyHMI / 3GL
(6FC5800-0AP60-0YB0)
● SINUMERIK 840D sl, SINUMERIK Integrate Run MyHMI / WinCC
(6FC5800-0AP61-0YB0)
Supplementary conditions
The following conditions must be met:
● It is only possible to switch between dialogs within a single operating area.
● User variables may not have the same names as system or PLC variables (also see List
Manual System Variables /PGAsl/).
● The dialogs activated by the PLC form a separate operating area (similar to measuring
cycle screens).
Tools
● UTF8-capable editor (e.g. the integrated editor of the user interface or Notepad)
● A graphics program is needed to create graphics/display images.
Note
When using HMI Operate in the NCU, note that all file names are written in lower case letters
(com, png, txt) on the CF card. This is required because of Linux.
File names are not case-sensitive on the PCU. However, it is recommended that you also use
lower case letters here, in case of a possible subsequent transfer to Linux.
Note
When saving configuration and language files, ensure that the coding is set to UTF-8 for the
editor you are using.
Storage paths
Note the following convention when storing the configuration files, language files, etc.
Storage locations
"Run MyScreens" configuration: [System oem directory]/proj
Configuration file: [System oem directory]/cfg
Language files: [System oem directory]/lng
Application
You can implement the following functions:
2.2 Example
Dialog 1
R parameters that can be written to (0 and 1) and geometry axis names are displayed in the
first dialog (input fields). The corresponding help screens are linked in for the two R parameters.
A context-sensitive help is linked in for the geometry axes. Further, the dialog includes
examples for separating lines (horizontal and vertical), toggle fields, input/output fields with
integrated unit selection and progress bars (with and without color change).
Dialog 2
MCS and WCS values are displayed in the second dialog. The dialog also contains examples
of progress bars with and without color change.
Figure 2-5 Progress bars with (right) and without (left) color change
Navigation
The first dialog is called using the "START" softkey in the diagnostics operating area. The
horizontal SK7 softkey is used.
Figure 2-6 Start softkey „START“ in the machine operating area, AUTO mode
You can call the second dialog from the first dialog with the "Next Mask" softkey. You can
return to the root screen of the operating area by pressing the "EXIT" softkey (see the screen
above).
Using the "EXIT" softkey, you can also return to the root screen of the operating area from the
second dialog (see the screen above). You can return to the first dialog via the "Back to Mask"
softkey.
Procedure
The necessary steps are described in the following chapters:
1. Creating the configuration file (COM file)
2. Saving the configuration file in the OEM directory
3. Creating the online help
4. Saving the online help in the OEM directory
5. Copying easyscreen.ini into the OEM directory
6. Registering the COM file in easyscreen.ini
7. Testing the project
; Press method
PRESS(HS7)
; LM or LS function
LM("MASK1")
; LM, specifying a com file
LM("MASK1","TEST.COM")
END_PRESS
; End identifier of start softkey
//END
; Press method
PRESS(VS7)
; Load an additional dialog
LM("MASK2")
; End identifier press method
END_PRESS
; Press method
PRESS(VS8)
; Load method
LOAD
H_SEPARATOR(230,1,7,1)
END_LOAD
; Change method
CHANGE(VAR5)
; Function PI_START
PI_START("/NC,201,_N_SETUFR")
; End identifier change method
END_CHANGE
; Press method
PRESS(RECALL)
; Return to the calling mask
LM("MASK1")
; End identifier press method
END_PRESS
; Press method
PRESS(VS7)
; Return to the calling mask
LM("MASK1")
; End identifier press method
END_PRESS
; Press method
PRESS(VS8)
; Exit the dialog to the standard application
EXIT
; End identifier press method
END_PRESS
; Dialog end identifier
//END
Storage path
Save the configuration file diag.com under the following path:
[System oem directory]/proj
Storage path
Save the HTML file sinumerik_md_1.html for the English help under the following path:
[System oem directory]/hlp/eng
You must create a folder for additional languages (e.g. chs, deu, esp, fra, ita …).
A list of language codes is provided in the Appendix.
Storage path
Copy the file easyscreen.ini from the directory
[System SIEMENS directory]/cfg
to the directory
[System oem directory]/cfg
Adaptation in easyscreen.ini
Make the following change in the easyscreen.ini in the OEM directory. You have thus registered
the diag.com configuration file.
;########################
;# AREA Diagnosis #
;########################
;<===============================================================>
;< OEM Softkey on first horizontal Main Menu >
;< SOFTKEY position="7" >
;<===============================================================>
StartFile28 = area := AreaDiagnosis, dialog:= SlDgDialog, menu := DgGlobalHu, startfile := diag.com
Introduction
The description of new user interfaces is stored in configuration files. These files are
automatically interpreted and the result displayed on the screen. Configuration files are not
stored in the software supplied and must be set up by the user.
A UTF-8-capable editor (e.g. the integrated editor of the user interface or Notepad) is used to
create the configuration files and language files. The description can also be explained using
comments. A ";" is inserted as comment character before every explanation.
Note
When saving configuration and language files, ensure that the coding is set to UTF-8 for the
editor you are using.
However, keywords - also in an UTF-8-coded COM file - may only comprise characters that
are contained in the ASCII character set. Otherwise the interpretation and therefore the display
of the screen forms/dialogs cannot be guaranteed.
Configuration
Each HMI operating area has permanent start softkeys which can be used to access newly
generated dialogs.
In the event of a "Load a screen form" (LM) or a "Load softkey menu" (LS) call in a configuration
file, a new file name containing the object called can be specified. This makes it possible to
structure the configuration, e.g. all functions in one operating level in a separate configuration
file.
Note
Sequence
The specified sequence in the configuration file must be maintained.
Example:
6WDUWVRIWNH\
Start softkeys
One or more softkeys (start softkeys), which are used to initiate your own operating sequences,
are defined in the configuration files specified in easyscreen.ini.
The loading of a dedicated dialog is associated with a softkey definition or another softkey
menu. These are then used to perform the subsequent actions.
Pressing the start softkey loads the assigned dialog. This will also activate the softkeys
associated with the dialog. Variables will be output to the standard positions unless specific
positions have been configured.
You can use the <RECALL> key to close new user interfaces if you have not configured this
key for any other task.
Note
Calling dialogs in the PLC user program
Dialogs can be selected from the PLC as well as via softkeys: An interface signal is available
in DB19.DBB10 for signal exchange between the PLC → HMI.
Dialog-independent softkey
Start softkeys are dialog-independent softkeys which are not called from a dialog, but which
have been configured before the first new dialog. In order to access the start dialog or a start
softkey menu, the start softkey must be defined.
Programming
The definition block for a start softkey is structured as follows:
Start softkeys are configured in special files. The names of these files are stated in the
easyscreen.ini file. They usually have a name which is specific to an operating area (e.g.
startup.com for the startup area). The machine operating area represents an exception. There
are several mode-specific files in the machine operating area (ma_jog.com, ma_auto.com).
The softkey menu with the start softkeys is called "Start". Existing configurations for start
softkeys can still be used. The function whereby start softkeys are merged with the softkeys
for the respective HMI application (operating area) in the start softkey menu is not supported.
This means that until the first dialog call is made - in other words, the time at which full
functionality becomes available (e.g. execution of PRESS blocks) - menus or softkey menus
can only be replaced by others in their entirety.
This file is used as a template for your own configuration of the start softkey.
See also
Lists of start softkeys (Page 235)
PRESS method
The softkey is defined within the definition block and the "LM" or "LS" function is assigned in
the PRESS method.
If the start softkey definition is designated as a comment (semicolon (;) at beginning of line)
or the configuration file removed, the start softkey will not function.
Example
Softkey menus or dialogs that are possibly included are ignored. If a softkey has a command
without file information, e.g. LM ("test"), as the required softkey menu or dialog is contained in
the same file, then the corresponding file name is supplemented in the internal merge version
so that in this case, no changes are required. The merge configuration contained is then
subsequently displayed.
Overview
If "Run MyScreens" detects errors when interpreting the configuration files, these errors will
be written to the easyscreen_log.txt text file. Only errors of the currently selected dialog are
entered. Error entries from previously selected dialogs are deleted.
The file indicates:
● The action during which an error occurred
● The line and column number of the first faulty character
● The entire faulty line of the configuration file
● The entries made by the DEBUG function
Note
Each entry has a prefix with the current time stamp in square brackets. This can be helpful,
for example, when analyzing time-critical configurations.
Saving easyscreen-log.txt
The file easyscreen_log.txt is saved in the following directory:
[System user directory]/log
Syntax
The system does not start to interpret the syntax until the start softkey has been defined and
a dialog with start and end identifiers as well as a definition line has been configured.
//S(Start)
HS6=("1st screen")
PRESS(HS6)
LM("Maske1")
END_PRESS
//END
//M(Maske1)
DEF Var1=(R)
DEF VAR2 = (R)
LOAD
VAR1 = VAR2 + 1 ; Error message in log book, as VAR2 has no value
...
//END
LOAD
VAR2 = 7
VAR1 = VAR2 + 1 ;
...
[GENERAL]
HlpPicFixPos=true
Note:
The start position of help displays is positioned at the configured pixel position independent of
the resolution (default=true).
[GENERAL]
SymmetricalAspectRatio=false
DefaultLineHeight=18
DefaultLineSpacing=3
Notes:
● The "SymmetricalAspectRatio" entry determines whether the same aspect ratio is used in
the X and Y direction when adapting a configuration to a specific screen resolution.
– "false" (default): Fields and graphics are shortened in widescreen resolution in the Y
direction (asymmetrical elongation in relation to 640x480). For example, a square
configured in 640x480 is shortened vertically for a widescreen panel and becomes a
rectangle.
– "true": The same aspect ratio is used in the X and Y direction and fields and graphics
retain their originally configured proportions in relation to 640x480. For example, a
square configured in 640x480 remains a square in a widescreen panel.
● The entries "DefaultLineHeight" and "DefaultLineSpacing" can be used to specify the
default line height (default: 18 pixels) and the default line spacing (default: 3 pixels) in
relation to 640x480. They only take effect when no Y position or height is specified in the
configuration for the position of the short text or the input/output field.
[640x480]
MyPanel = x:=0, y:=220, width:=340, height:=174
[800x480]
MyPanel = x:=0, y:=220, width:=420, height:=174
...
Notes:
Note
When using HMI Operate in the NCU, note that all file names are saved in lower case letters
on the CF card (com, png, txt).
Note
Make sure that the coding is set to UTF-8 in the editor that you are using when saving the
configuration and language files.
Image files
Image files must be saved in the PNG format (xxx.png).
The data must be saved, e.g. for OEM modifications, under
[System oem directory]/ico/[Resolution]
For further information, see also Chapter Using display images/graphics (Page 52).
Example:
//M{VariantTest, HD="My Mask"}
Examples:
Examples:
Example:
Further details can be found in Chapter Defining dialog properties (Page 41), Section
"Programming".
Definition
A dialog is part of a user interface consisting of a display line, dialog elements and/or graphics,
an output line for messages and 8 horizontal and 8 vertical softkeys.
Dialog elements are:
● Variables
– Limits/toggle field
– Default setting of variables
● Help display
● Texts
● Attributes
● System or user variable
● Position of short text
● Position of input/output field
● Colors
Dialog properties:
● Header
● Graphic
● Dimension
● System or user variable
● Graphic position
● Attributes
Overview
The definition of a dialog (definition block) is basically structured as follows:
Within the dialog definition block, various variables that appear as dialog elements in the dialog,
as well as horizontal and vertical softkeys, are defined first. Different types of actions are then
configured in methods.
Description
The properties of the dialog are defined in the start identifier line of the dialog.
Programming
Note:
If, when configuring the masks, the mask attribute KM is explicitly set, then
this has a higher priority than the global setting in easyscreen.ini.
MA2 All fields are adjusted irrespective of the configured field sizes.
PA Optimized and pixel-precise stretching of the fields for higher resolutions
(Pixel Fine Adjustment)
Previously all field positions were calculated in relation to 640x480 and then
zoomed with the appropriate horizontal and vertical stretch factors. This
process has the disadvantage that rounding errors can occur with "unfav‐
orable stretch factors". For example, the field height or line spacing can
"jump" by a pixel from line-to-line. The "Pixel Fine Adjustment" mode can
be used to prevent this as the field positions are determined directly in the
current resolution.
//M(MyMask/"My Mask"/////PA1)
This setting can also be made globally for all Run MyScreens masks in the
easyscreen.ini, e.g.
[GENERAL]
DefaultPixelFineAdjustment=1
If the mask attribute PA is set explicitly in the mask configuration, it has a
higher priority than the global setting in the easyscreen.ini.
If a mask is displayed with Font Adjustment = FA1, then the Pixel Fine
Adjustment mode is also automatically active for this mask.
(See also Chapter SmartOperation and MultiTouch operation (Page 37))
PA0 Stretching as previously, i.e. the positions are calculated in relation to
640x480 and then stretched.
(For compatibility reasons: Default)
PA1 Optimized and pixel-precise stretching of the fields for higher resolutions
FA Field height and line spacing proportional to the font (Font Adjustment)
This setting can also be made globally for all Run MyScreens masks in the
easyscreen.ini, e.g.
[GENERAL]
DefaultFontAdjustment=1
If the mask attribute FA is set explicitly in the mask configuration, then this
has a higher priority than the global setting in easyscreen.ini.
The settings for the DefaultLineHeight and DefaultLineSpacing have no
significance when Font Adjustment mode is active.
(See also Chapter SmartOperation and MultiTouch operation (Page 37))
FA0 Field height and line spacing are stretched as previously. (For compatibility
reasons: Default)
FA1 Field height and line spacing are set proportional to the font (automatically
sets mask attribute PA=1)
FA2 Same as FA1, but the X coordinate and the field width are also stretched
proportionally to the font
(Automatically sets mask attribute PA=1)
(Only possible in conjunction with attribute XG=1!)
MC Mask background color (mask color)
Example:
Set mask background color blue (= 6)
//M(MyMask/"MyMask"//////6)
or
PRESS(HS1)
MC=6
END_PRESS
List of the mask-specific lan‐ separated by a comma
guage files
Example
//S(Start)
HS7=("Example", se1, ac7)
PRESS(HS7)
LM("Mask2")
END_PRESS
//END
//M(Mask2/"Example 2 : showing graphic"/"example.png")
HS1=("new%nHeader")
HS2=("")
HS3=("")
HS4=("")
HS5=("")
HS6=("")
HS7=("")
HS8=("")
VS1=("")
VS2=("")
VS3=("")
VS4=("")
VS5=("")
VS6=("")
VS7=("")
VS8=("")
PRESS(HS1)
Hd= "new Header"
END_PRESS
...
//END
See also
Programming example for the "Custom" area (Page 224)
Dialog element
The term "dialog element" refers to the visible part of a variable, i.e. short text, graphics text,
input/output field, unit text and tooltip. Dialog elements fill lines in the main body of the dialog.
One or more dialog elements can be defined for each line.
Variable properties
All variables are valid in the active dialog only. Properties are assigned to a variable when it
is defined. The values of dialog properties can be accessed within methods (e.g. a PRESS
method).
Programming - Overview
The single parameters to be separated by commas are enclosed in round brackets:
See also
Variable parameters (Page 71)
Overview
Multiple variables can also be represented in a dialog on one line. In this case, the variables
are all defined in the configuration file on a single definition line.
To make individual variables in the configuration file more legible, the definition lines can be
wrapped after every variables definition and following comma.
The key word "DEF" always indicates the beginning of a new line:
Note
When configuring multi-column dialogs, please observe that a large number of columns might
slow down the system!
● Change password
● Delete password
Note
Password functionality is provided with these dialogs. The dialogs do not correspond to the
dialogs of SINUMERIK Operate.
The dialogs can be called either via the Load softkey (LS) function or the Load mask (LM)
function:
1. Call via the Load softkey (LS) function:
LS("Passwd","slespasswd.com",1)
Extension of the vertical softkeys:
– Softkey 1: Set password
– Softkey 2: Change password
– Softkey 3: Delete password
2. Alternatively, the three masks can be directly jumped to by calling the (LM) function:
– Set password: LM("PWD_SET", "slespasswd.com",1)
– Change password: LM("PWD_CHG", "slespasswd.com",1)
– Delete password: LM("PWD_CLEAR", "slespasswd.com",1)
Use of graphics
A distinction is made between:
● Display images / graphics in the graphic area.
● Help displays illustrating, for example, individual variables, which are superimposed in the
graphic area.
● More Help displays can be configured instead of short text or an input/output field, which
you position where you like.
Storage locations
The image matching the resolution of the connected monitor is searched for in the associated
resolution directories in the following sequence:
If the image is not displayed or not found, copy it into one of the following directories for a
resolution of 640 x 480 pixels:
Note
With the different panel resolutions, the images are positioned proportionally.
Definition
The term softkey menu is used to refer to all the horizontal and vertical softkeys displayed on
a screen form. In addition to the existing softkey menus, it is possible to define other menus,
which partially or completely overwrite the existing menus.
The names of the softkeys are predefined. Not all softkeys need to be assigned.
HSx x 1 - 8, Horizontal softkeys 1 to 8
VSy y 1 - 8, Vertical softkeys 1 to 8
The definition of a softkey menu (softkey menu definition block) is basically structured as
follows:
Description
Properties are assigned to softkeys during definition of the softkey menu.
Programming
Note
Enter %n in the softkey text to create a line break.
A maximum of 2 lines with 9 characters each are available.
Example
Description
The softkey properties Text, Access Level and Status can be changed in the methods during
runtime.
Programming
Example
//S(Start)
HS7=("Example", ac7, se1)
PRESS(HS7)
LM("Maske3")
END_PRESS
//END
VS1=("")
VS2=("")
VS3=("")
VS4=("\\sp_ok.png",,SE1)
VS5=(["\\sp_ok_small.png","OEM Text"],,SE1)
VS6=("")
VS7=(SOFTKEY_OK,,SE1)
VS8=(SOFTKEY_CANCEL,,SE1)
PRESS(VS4)
EXIT
END_PRESS
PRESS(VS5)
EXIT
END_PRESS
PRESS(VS7)
EXIT
END_PRESS
PRESS(VS8)
EXIT
END_PRESS
//END
Overview
Language-dependent texts are used for:
● Softkey labels
● Headings
● Help texts
● Any other texts
The language-dependent texts for dialogs are stored in text files.
The text files are stored in the following directories:
● [System user directory]/lng
● [System oem directory]/lng
● [System add_on directory]/lng
Note
The text files must be saved in the same way as the project files.
For example:
[System user directory]/lng/[Text file]
[System user directory]/proj/[Configuration file]
[LANGUAGEFILES]
LngFile03 = user.txt ;->user<_xxx>.txt (e.g.: user_eng.txt)
In this instance, the user.txt file has been chosen as an example of a text file. The name can
always be freely selected. Depending on the language of the texts within the file, the relevant
language code must be added using the following syntax. An underscore followed by the
relevant language identifier is added after the name e.g. user_eng.txt.
Note
You must not use LngFile01 and LngFile02 for user texts because they are already assigned
in the standard easyscreen.ini.
See also
List of language codes used in file names (Page 239)
If no language files have been defined in the mask, then a search is only made in the language
files specified in easyscreen.ini.
Note
The English language file is used (default) if a language file is not available in the currently
selected language.
Examples:
You can also use this procedure for the start softkeys:
Note
Make sure that the coding is set to UTF-8 in the editor that you are using when saving the
configuration and language files.
Parameters 2 and 3 are separated by blanks and act as control characters for alarm text output.
To ensure that the text format is identical to that of the alarm texts, you must set zero.
Online help
An online help for the configured dialogs and elements can be created in the HTML format.
The syntax and procedure for the online help is essentially the same as for SINUMERIK
Operate.
If an online help is configured for an input field, then the standard screens of the online help
are used to display the user-specific online help:
DEF RFP=(R//1/,"RFP","RFP"///////"sinumerik_md_1.html","9006")
Note
As a result of LINUX, the HTML file must be written in lower case letters!
The HTML file is saved in the following directory, e.g. for English.
[System user directory]/hlp/eng
[System oem directory]/hlp/eng
[System add_on directory]/hlp/eng
You must create the directories for additional languages corresponding to the language codes
(see appendix).
References
Commissioning Manual "Base software and operating software" (IM9), Chapter "OEM-specific
online help"
Variable value
The major property of a variable is its value.
The value of variables can be assigned by means of:
● Default settings when defining variables
● Assignment to a system or user variable
● A method
Programming
Variable status
The "Variable status" property scans a variable for valid content during runtime. This property
can be read and written with the value FALSE = 0.
Programming
Syntax: Identifier.vld
Description: Variable status vld (validation)
Parameter: Identifier: Name of the variable
The result of the scan can be:
FALSE = invalid value
TRUE = valid value
Example: IF VAR1.VLD == FALSE
VAR1 = 84
ENDIF
Help variables
Help variables are internal arithmetic variables. Arithmetic variables are defined like other
variables, but have no other properties apart from variable value and status, i.e. Help variables
are not visible in the dialog. Help variables are of the VARIANT type.
Programming
Example:
LOAD
OTTO = "Test" ; The value "Test" is assigned to help variable Otto.
END_LOAD
LOAD
OTTO = REG[9].VAL ; The value of the register is assigned to help variable
END_LOAD Otto
IF VAR1.VLD == FALSE
VAR1 = 84
ENDIF
PRESS(HS1)
ACHSE=ACHSE+1
WEG.VAR="$AA_DTBW["<<ACHSE<<"]" ;Address axis address via variable
END_PRESS
5.3 Example 1: Assigning the variable type, texts, help display, colors,
tooltips
Example 1a
The following example defines a variable for which the properties variable type, texts, help
display and colors are set.
Example 1b
The following example defines a variable for which the properties variable type, default setting,
texts, tooltip, input mode and position of short text are set.
See also
Variable parameters (Page 71)
5.4 Example 2: Assigning the Variable Type, Limits, Attributes, Short Text
Position properties
Example 2
The following example defines a variable for which the properties variable type, limits, input
mode, alignment and position are set.
See also
Variable parameters (Page 71)
Example 3
The following example defines a variable for which the properties variable type, default setting,
system or user variable and position are set.
See also
Variable parameters (Page 71)
Example 4a
Various entries in the toggle field:
DEF Var1 = (I/* 0,1,2,3) ;Simple toggle field to toggle numeric values
DEF Var2 = (S/* "On", "Off") ;Simple toggle field to toggle strings
DEF Var3 = (B/* 1="On", 0="Off") ;Extended toggle field to toggle numeric values whereby a
display text is assigned to each numeric value
DEF Var4 = (R/* ARR1) ;Toggle field which obtains its values to be toggled from an
array
Example 4b
The list field corresponds to the configuration of a toggle field, but the display type for the list
field (variable attribute DT = 4) must also be set.
Example 5
Displaying an image instead of a short text: The size and position of the image is defined under
"Position of input/output field (left, top, width, height)".
Example 6a
Progress bar with two color changes:
To use a progress bar with color change, the display mode DT (DisplayType) must be set to
1.
The orientation of the progress bar is determined via the attribute display option DO
(DisplayOption):
0: From left to right (default)
1: From right to left
2: From bottom to top
3: From top to bottom
A MIN and a MAX value must be specified for the display of the progress bar (in the example
MIN: 0, MAX: 150).
Depending on the current value of the variable PROGGY0, this setting already displays a
progress bar with the foreground color 3 (= dark green) and the background color 4 (= light
gray).
Optionally, one or two signal values SVAL1 and SVAL2 (limit parameters) can be defined (in
the example SVAL1: 50 and SVAL2: 100). With these signal values, the foreground color of
the progress bar changes. The appropriate signal colors are specified via parameters SC1
and SC2 (in the above example SC1: 9 (= yellow) and SC2: 7 (=red)).
The following rule applies when specifying limit values for the progress display:
MIN < SVAL1 < SVAL2 < MAX.
Example 6b
Progress bar without color change:
To use a progress bar without color change, the display mode DT (DisplayType) must be set
to 2.
The orientation of the progress bar is determined via the attribute display option DO
(DisplayOption) (see description for example 6a).
A MIN and a MAX value must be specified for the display of the progress bar (in the example
MIN: 0, MAX: 150).
Depending on the current value of the variable PROGGY0, this setting displays a progress
bar with the foreground color 6 (= blue) and the background color 10 (= white).
Example 7
To implement a field with hidden input, e.g. to enter a password, then display mode DT must
be set to 5. Asterisks are then displayed instead of the entered characters.
DEF VAR_SET_PWD=(S//""//DT5)
Variable type: STRING
Default setting: Empty string
Attributes:
Display mode DT: 5 (password input mode)
Parameter overview
The following overview provides a brief explanation of the variable parameters. Subsequent
chapters contain a more detailed description.
Parameter Description
Variable type (Page 77) The variable type must be specified.
R[x]: REAL (+ digit for the decimal place)
I: INTEGER
S[x]: STRING (+ digit for string length)
C: CHARACTER (individual character)
B: BOOL
V: VARIANT
Parameter Description
Limits (Page 66) Limit value MIN, limit value MAX
Default setting: Empty
The limit values are separated by a comma. Limits can be specified for types I, C and R
in decimal formats or as characters in the form "A", "F".
Optionally, two signal colors SC1 and SC2 can be configured for the display of a progress
bar with color change (variable attribute DT = 1) which are displayed as the respective
foreground color of the bar when the signal value SVAL1 or SVAL2 is exceeded. The
signal values are specified as integer values.
See application example for Progress bar (Page 68).
Default setting (Page 81) If no default setting has been configured and no system or user variable has been assigned
to the variable, the first element of the toggle field is assigned. If no toggle field has been
defined, there is no default setting, which means the status of the variable is "not calcu‐
lated".
Default setting: No default
Toggle field (Page 80) List with predetermined entries in the IO field: The list is initiated by a *; the entries are
separated by a comma. The entries can be assigned a value.
For the toggle field, the entry for the limit is interpreted as a list. If only one * is entered,
a variable toggle field is created.
Default setting: None
Texts (Page 65) The sequence is specified. Instead of a short text, an image can also be displayed.
Default setting: Empty
Long text: Text in the display line
Short text: Name of the dialog element
Graphic text: Text refers to the terms in the graphics
Unit text: Unit of the dialog element
Tooltip Serves as brief information in a screen form configuration for
the display and toggle fields. The information is configured via
plain text and language text ID.
Parameter Description
Attributes (Page 66) The attributes influence the following properties:
● Display mode
● Display option
● Update rate
● Toggle symbol
● Tooltip
● Input mode
● Access level
● Alignment of short text
● Font size
● Limits
The attributes are separated by commas and appear in any order. A definition can be
made for each component.
Display mode dt0: Standard (input/output field or toggle field) (default)
dt1: Progress bar with color change
dt2: Progress bar without color change in the Operate style
dt4: List field
dt5: Password input mode (asterisk)
Display option Particularly, e.g. for the display modes dt1 and dt2 (progress bars), a
display option may also have to be configured in combination.
do0: From left to right (default)
do1: From right to left
do2: From bottom to top
do3: From top to bottom
Update rate The attribute UR (update rate) controls the update of the display and
therefore the processing of the associated, configured CHANGE block
of variables or grid columns. Depending on the configuration, the CPU
load can be drastically reduced and therefore shorter response times
achieved on the user interface.
ur0: SlCap::standardUpdateRate() (currently = 200 ms, default value)
ur1: 50 ms
ur2: 100 ms
ur3: 200 ms
ur4: 500 ms
ur5: 1000 ms
ur6: 2000 ms
ur7: 5000 ms
ur8: 10000 ms
Toggle symbol tg0: Toggle symbol off (default)
tg1: Toggle symbol on
If the attribute TG is set to 1, the toggle symbol also appears in the
tooltip of the input field.
Example:
DEF OFFS = (R//123.456/,,,,"My ToolTip"/TG1)
Parameter Description
Tooltip The tooltip text can also be changed during runtime via the variable
property "TT".
Example:
PRESS(VS1)
MyVar.TT = "My new ToolTip"
END_PRESS
or
DEF MyVar=(R///,,,,"My ToolTip-text")
Input mode wr0: IO field invisible, short text visible
wr1: Read (no focus possible for input)
wr2: Read and write (line appears in white)
wr3: wr1 with focus
wr4: All variable elements invisible, no focus possible
wr5: The value entered is saved immediately on every keystroke (in
contrast to wr2, where it is only saved when the field is exited or RE‐
TURN is pressed).
Default setting: wr2
Access level Empty: Can always be written
(Page 238) ac0...ac7: Protection levels
If the access level is not adequate, then the first line is displayed in
gray, default setting: ac7
Alignment of al0: Left-justified
short text al1: Right-justified
al2: Centered
Default setting: al0
Font size fs1: Default font size (8 pt.)
fs2: Double font size
Default setting: fs1
The clearances between the lines is defined. With the default font size,
16 lines will fit into the dialog. Graphics and unit text can only be con‐
figured in the default font size.
Limits Consequently, it is possible to check whether the values of the variable
are within the MIN and MAX limits specified.
Default setting: Determined by specified limits
li0: No check
li1: Check with respect to min.
li2: Check with respect to max.
li3: Check with respect to min. and max.
Behavior when cb attributes specified for a variable in a variables definition take pri‐
opening ority over the cb default setting in the dialog definition. Multiple attrib‐
utes are separated by commas (see also Behavior when opening the
dialog (attribute CB) (Page 240)).
CB0: The CHANGE method is triggered when the screen is displayed if the
variable has a valid value at this time (e.g. through default setting or
CB1: NC/PLC variable).
Parameter Description
The CHANGE method is not explicitly triggered when the screen is
displayed. If the variable has a configured NC/PLC variable, then the
CHANGE method is of course still called.
Help display (Page 65) Help display file: Name of the png file
Default setting: Empty
The name of the Help display file appears in double quotation marks. The display appears
automatically (instead of the previous graphic) if the cursor is positioned on this variable.
System or user variable System or user data from the NC/PLC can be assigned to the variable. The system or
(Page 67) user variable appears in double quotation marks.
Reference: List Manual System Variables, /PGAsl/
Position of short text (Page 82) Position of short text (distance from left, distance from top, width)
The positions are entered in pixels and relate to the upper left-hand corner of the main
body of the dialog. The entries are separated by commas.
Position of input/output field Position of input/output field (distance from left, distance from top, width, height)
(Page 82) The positions are entered in pixels and relate to the upper left-hand corner of the main
body of the dialog. The entries are separated by commas. If this position changes, the
positions of the short text, graphic text and unit text also change.
Colors (Page 65) Foreground and background colors for input/output fields, short texts, graphic texts, unit
texts and signal colors for progress bars:
The colors are separated by a comma.
For specification of the color, see Chapter List of colors (Page 238).
Default setting for input/output field: Foreground color: Black, background color: White
The default colors of the input/output field depend on the "wr" write mode:
Default setting for short text, graphic text, unit text: Foreground color: Black, background
color: Transparent.
Optionally, two signal colors SC1 and SC2 can be configured for the display of a progress
bar with color change (variable attribute DT = 1) which are displayed as the respective
foreground color of the bar when the signal value SVAL1 or SVAL2 is exceeded.
See application example for Progress bar (Page 68).
The colors are expected in the following order in the variables definition:
1. Foreground color of the input/output field: FC
2. Background color of the input/output field: BC
3. Foreground color of the short text: FC_ST
4. Background color of the short text: BC_ST
5. Foreground color of the graphic text: FC_GT
6. Background color of the graphic text: BC_GT
7. Foreground color of the unit text: FC_UT
8. Background color of the unit text: BC_UT
9. Signal color 1
10. Signal color 2
Parameter Description
Online help file (Page 61) The name of the online help file appears in double quotation marks.
I/O field with integrated unit se‐ You can use the input/output fields with integrated unit selection to toggle between differ‐
lection ent units. If the cursor is moved to the input field, the integrated unit selection is highlighted
(focus does not have to be explicitly placed on it). A tooltip with a toggle symbol is also
displayed with the appropriate reference to this functionality.
Examples:
DEF VarEdit=(R////////200,,100///"VarTgl")
VarTgl=(S/*0="mm",1="inch"/0//WR2////302,,40)
or
DEF VarEdit_2={TYP="R", VAL=1.234, X=200, W=100,
LINK_TGL="vartgl_2"},
VARTgl_2={TYP="S", TGL="* 0=""mm"", 1=""inch""",WR=2, X=302,
W=40}
See also
Extended configuration syntax (Page 36)
Display format
B Binary
D Decimal signed
H Hexadecimal
No data Decimal signed
Memory utilization
B Byte
W Word
D Double word
BU Byte, Unsigned
WU Word, Unsigned
DU Double word, Unsigned
Programming
The data type of variables can be checked:
B Binary
D Decimal signed
H Hexadecimal
unsigned
With the addition of U for Unsigned
● For REAL data types, only the number of places after the decimal point can be changed.
Changing the type is illegal and generates an error message in the easyscreen_log.txt. file.
Example:
Var1.typ = "IBW"
Var2.typ = "R3"
Numerical formats
Numbers can be represented in either binary, decimal, hexadecimal or exponential notation:
Binary B01110110
Decimal 123.45
Hexadecimal HF1A9
exponential -1.23EX-3
Examples:
VAR1 = HF1A9
REG[0]= B01110110
DEF VAR7 = (R//-1.23EX-3)
Note
When codes are generated with the "GC" function, only numerical values in decimal or
exponential notation are evaluated, but not those in binary or hexadecimal notation.
See also
Variable parameters (Page 71)
Description
The toggle field extension function displays texts (entries in toggle field) as a function of NC/
PLC variables. A variable, which makes use of a toggle field extension, is read-only. The list
of the toggle field is opened by pressing the ENTER key.
Programming
Toggle-field-dependent displays
The toggle field is overlaid with graphics, which change depending on the value of the memory
byte. If the value of the memory byte is 1, "image1.png" will appear. If it is 2, "image2.png" will
appear.
The size and position of the image is defined under "Position of IO field (left, top, width, height)".
[VirtualKeyboard]
See also
Variable parameters (Page 71)
Overview
A variable can assume various states depending on whether a default value, or a system or
user variable, or both, is assigned to the variable field (input/output field or toggle field), (not
calculated: toggling is only possible if a valid value has been assigned to the variable).
See also
Variable parameters (Page 71)
5.14 Details on the position of the short text, position of the input/output
field
Overview
The short text and graphic text, as well as the input/output field and unit text, are each treated
like a unit, i.e., position settings for short text apply to the graphic text and data for the input/
output field and to unit text.
Programming
The configured position entry overwrites the default value, i.e., only one value can be changed.
If no position settings have been configured for subsequent screen form elements, then the
position settings for the preceding screen form element are applied.
The default setting is used if positions are not specified for any of the dialog elements. The
column width for the short text and input-output field is calculated as standard for each line
from the number of columns and maximum line width, i.e. column width = maximum line width/
number of columns.
The width of the graphics and unit text is predefined and optimized to suit the requirements of
programming support. If graphics or unit text has been configured, the width of the short text
or I/O field is reduced accordingly.
The order of short text and I/O field can be reversed by position settings.
Distance between the input/output field and unit field and width of the unit field
You can configure the distance between an input/output field and a unit field as well as the
width of the unit field.
In the definition line, in the section for the input/output position, enter the distance from the
input/output field to the unit field, separated by a comma (e.g. 7 pixels) and/or the width of the
unit field (e.g. 60 pixels):
DEF VarDT=(R3//0.000/,"DT",,"s"////0,,24/39,,71,,7,60)
Or:
DEF VarDT={TYP="R3", VAL="0.000", ST="DT", UT="s", TXT_X=0,
TXT_W=24, X=39, W=71, UT_DX=7, UT_W=60}
In this case, the distance between the input/output field/unit field and/or the width of the unit
field have/has been configured and the following points should be taken into account:
● The configured width of the input/output field does not include the fixed width of the unit
field (this is fixed at 50 pixels). This means that you directly configure the width of the input/
output field.
● A 50 pixel width applies as default if a width is not configured for the unit field.
● 0 pixels applies as default if a distance is not configured between the input/output field /
unit field.
Example
In the following example, the associated toggle field F_Unit is automatically set with a distance
of 7 pixels to the input/output field of variable VarF , and with a width of 59 pixels .
DEF VarF=(R//0.0/,"F",,,////0,,24/39,,85,,7,59///"F_Unit"), F_Unit =
(I/*3="mm/min", 1="mm/U"/3// ////181,,155)
See also
Variable parameters (Page 71)
Strings
Strings can be used as part of the configuration. These allow text to be displayed dynamically
or different texts to be chained for the purpose of code generation.
Rules
The following rules must be observed with regard to string variables:
● Logic operations are processed from left to right.
● Nested expressions are solved from the inside outwards.
● No distinction is made between uppercase and lowercase type.
● String variables are generally displayed left justified.
Strings can be deleted simply by assigning a blank string.
Strings can be appended after the equality sign using the operator "<<". Quotation marks (")
in the string are represented by two successive quotation mark symbols. Strings can be
checked for equality in IF instructions.
Example
Default settings for the following examples:
VAR1.VAL = "This is an"
VAR8.VAL = 4
VAR14.VAL = 15
VAR2.VAL = "Error"
$85001 = "This is an"
$85002 = "Alarm text"
Editing strings:
● Chaining of strings:
VAR12.VAL = VAR1 << " Error." ;Result: "This is an error"
● Deleting a variable:
VAR10.VAL = "" ;Result: Blank string
● Setting a variable with a text variable:
VAR11.VAL = VAR1.VAL ;Result: "This is an"
● Data type matching:
VAR13.VAL ="This is the " << (VAR14 - VAR8) << ". error"
;Result: "This is the 11th error"
● Treatment of numerical values:
VAR13.VAL = "Error" << VAR14.VAL << ": " << $85001 << $85002
;Result: "Error 15: "This is an alarm text"
IF VAR15 == "Error" ;Strings in IF statement
VAR16 = 18.1234
;Result: VAR16 equals 18.1234,
;if VAR15 equals "Error".
ENDIF
See also
STRING functions (Page 155)
Description
The CURPOS variable calls or manipulates the position of the cursor in the active input field
of the current dialog. The variable shows how many characters are in front of the cursor. If the
cursor is located at the start of the input field, then CURPOS assumes the value of 0. If the
value of CURPOS is changed, then the cursor is positioned at the appropriate location in the
input field.
In order to be able to respond to changes in the variable value, it is possible to monitor for
changes using a CHANGE method. If the value of CURPOS changes, then a jump is made to
the CHANGE method and the instructions contained there are executed.
Description
The CURVER (CURrent VERsion) property allows the programming to be adapted in order to
handle different versions. The CURVER variable is read-only.
Note
Even if previously recompiled with an older version, the code is automatically generated with
the most recent version. The "GC" command always generates the most recent version. An
additional identifier indicating the generated version is inserted in the user comment of the
generated code in versions > 0.
Rules
The most recent dialog with all its variables is always displayed.
● Variables used previously may not be changed.
● New variables are inserted in the existing (cycle) programming in arbitrary order.
● It is not permissible to delete variables from a dialog from one version to the next.
● The dialog must contain all variables of all versions.
Example
Description
The ENTRY variable can be used to check by what method a dialog has been called.
Programming
Syntax: ENTRY
Description: The ENTRY variable is a read only variable.
Return Value: The result of the scan can be:
0= No programming support
1= Start of a screen via softkey; no code has been generated yet (default
as configured)
2 = Start of a screen via softkey; code has been generated
(default from the code generated last by this screen)
3 = Recompilation with user comment (# lines)
4 = Code_type = 0: NC code with user comment (# lines)
5 = Code_type = 1: NC code without user comment (# lines)
Example
IF ENTRY == 0
DLGL ("The dialog was not called under programming")
ELSE
DLGL ("The dialog was called under programming")
ENDIF
Description
Variable ERR checks whether the preceding line has been executed correctly.
Programming
Syntax: ERR
Description: The ERR variable is read-only.
Return value: The result of the scan can be:
FALSE = previous line was executed error-free
TRUE = previous line was not executed error-free
Example
Description
Variable FILE_ERR can be used to check whether the preceding GC or CP command has
been executed correctly.
Programming
Syntax: FILE_ERR
Description: The FILE_ERR variable is read-only.
Example
CP("D:\source.mpf","E:\target.mpf")
; Copy from source.mpf to E:\tar-
get.mpf
IF FILE_ERR > 0 ; Query whether error has occurred
IF FILE_ERR == 1 ; Query specific error numbers and
output associated error text
VAR5 = "Drive/path not available"
ELSE
IF FILE_ERR == 2
VAR5 = "Path/file access error"
ELSE
IF FILE_ERR == 3
VAR5 = "incorrect file name"
ENDIF
ENDIF
ENDIF
ELSE
VAR5 = "All OK" ; If no errors have occurred in CP
(or GC), "All OK" is output
ENDIF
Description
With the variable FOC, the input focus (current active input/output field) is controlled in a dialog.
The reaction of the cursor left, right, up, down as well as PGUP, PGDN are predefined.
Note
The FOC function must not be initiated as a result of a navigation event. The cursor position
may only be changed in softkey PRESS methods, CHANGE methods, etc.
The FOC function cannot be applied to variables with input mode wr = 0 and wr = 4 or to Help
variables.
Programming
Syntax: FOC
Description: The variable can be read and written.
Return value: Read The result is the name of the variable to which the FOC func‐
tion has been applied.
Write It is possible to assign either a string or a numerical value. A
string is interpreted as a variable name and a numerical value
as a variable index.
Example
See also
FOCUS (Page 103)
Description
The current access level can be queried in the configuration with the screen property
S_ALEVEL.
Programming
Syntax: S_ALEVEL
Description: Query of the current access level
Return value: 0: System
1: Manufacturer
2: Service
3: User
4: Key switch 3
5: Key switch 2
6: Key switch 1
7: Key switch 0
Example
REG[0] = S_ALEVEL
See also
ACCESSLEVEL (Page 100)
Description
The S_CHAN variable determines the number of the current channel for display or evaluation
purposes.
Programming
Syntax: S_CHAN
Description: Query of the current channel number
Return value: Channel number
Example
REG[0] = S_CHAN
See also
CHANNEL (Page 102)
Description
The current control name can be queried in the configuration with the screen property
S_CONTROL.
Programming
Syntax: S_CONTROL
Description: Query of the current control name
Return value: The control name is the section name in the mmc.ini
Example
REG[0] = S_CONTROL
See also
CONTROL (Page 102)
Description
The current language can be queried in the configuration with the screen property S_LANG.
Programming
Syntax: S_LANG
Description: Query of the current language
Return value: Language code from resources.xml, e.g. "deu", "eng", etc.
Example
REG[0] = S_LANG
See also
LANGUAGE (Page 104)
Description
The screen property S_NCCODEREADONLY is only relevant when a cycle is recompiled in
the editor with a "Run MyScreens" dialog. S_NCCODEREADONLY determines whether a
recompiled NC code from the editor can be changed or not.
The following applies for the return value:
● TRUE: The recompiled NC code from the editor can be changed
● FALSE: The recompiled NC code from the editor cannot be changed (read-only), because,
for example, it is already in the preprocessing (= TRUE).
Description
The current resolution or its X and Y component can be queried in the configuration with the
screen properties S_RESX and S_RESY.
Example
REG[0] = S_RESY
See also
RESOLUTION (Page 109)
Overview
The following operators can be used when programming:
● Mathematical operators
● Relational operators
● Logic (Boolean) operators
● Bit operators
● Trigonometric functions
Overview
Example: VAR1.VAL = 45 * (4 + 3)
ROUND
The ROUND operator is used to round off numbers with up to 12 decimal places during
execution of a dialog configuration. The variable fields cannot accept the decimal places in the
display.
Use
ROUND is controlled by the user with two parameters:
VAR1 = 5.2328543
VAR2 = ROUND( VAR1, 4 )
Result: VAR2 = 5.2339
VAR1 contains the number to be rounded. The parameter “4” indicates the number of decimal
places in the result, which is placed in VAR2.
Trigonometric functions
Note
The functions operate with radian measure. The functions SDEG() and SRAD() can be used
for conversion.
Mathematical functions
Example
Constants
Constants
PI 3.14159265358979323846
FALSE 0
TRUE 1
Example: VAR1.VAL = PI
Comparison operators
Comparison operators
== Equal to
<> Not equal to
> Greater than
< Less than
>= Greater than or equal to
<= Less than or equal to
Example:
IF VAR1.VAL == 1
VAR2.VAL = TRUE
ENDIF
Conditions
The nesting depth is unlimited.
Overview
SHL operator
Bits are shifted to the left using the SHL (SHIFT LEFT) operator. You can specify both the
value to be shifted and the number of shift increments directly or via a variable. If the limit of
the data format is reached, the bits are shifted beyond the limit without displaying an error
message.
Use
Example
PRESS(VS1)
SHR operator
Bits are shifted to the RIGHT using the SHR (SHIFT RIGHT) function. You can specify both
the value to be shifted and the number of shift increments directly or via a variable. If the limit
of the data format is reached, the bits are shifted beyond the limit without displaying an error
message.
Use
Example
PRESS(VS1)
VAR01 = 16 SHR 2 ; Result = 4
VAR02 = VAR02 SHR VAR04 ; Convert content of VAR02 to 32-bit unsigned
, and shift content to right by number of bits
specified in VAR04. Then convert 32-bit value back
to format of variable VAR02.
END_PRESS
6.2 Methods
Overview
Various types of event (exit input field, actuate softkey) can initiate specific actions in dialogs
and dialog-dependent softkey menus (softkey menus that are called from a newly configured
dialog). These actions are configured in methods.
The following table shows the basic principle used to program a method:
6.2.1 ACCESSLEVEL
Description
The ACCESSLEVEL method is run through when the current access level has changed for
an opened screen.
Programming
Syntax: ACCESSLEVEL
<instructions>
END_ACCESSLEVEL
Description: Access level
Parameters: - None -
See also
Variable S_ALEVEL (Page 90)
6.2.2 CHANGE
Description
CHANGE methods are executed if a variable value changes, i.e., variable calculations that
are performed as soon as a variable value changes are configured within a CHANGE method.
There are two types of CHANGE method, i.e., element-specific and global:
● The element-specific CHANGE method is executed if the value of a specified variable
changes. If a system or user variable is assigned to a variable, cyclic updating of the variable
value can be configured in a CHANGE method.
● The global CHANGE method is executed if the value of any variable changes and no
element-specific CHANGE method has been configured.
"Element-specific" programming
Syntax: CHANGE(Identifier)
...
END_CHANGE
Description: Changes the value of a specific variable
Parameters: Identifier Name of the variable
Example
"Global" programming
Syntax: CHANGE()
...
END_CHANGE
Description: Changes any variable value
Parameters: - None -
Example
CHANGE()
EXIT ; If any of the variable values change, the di-
alog will be terminated.
END_CHANGE
See also
Behavior when opening the dialog (attribute CB) (Page 240)
6.2.3 CHANNEL
Description
The CHANNEL method is run through when the current channel has changed for an opened
screen, i.e. a channel switchover has been performed.
Programming
Syntax: CHANNEL
<instructions>
END_CHANNEL
Description: Channel switchover
Parameters: - None -
See also
S_CHAN variable (Page 90)
6.2.4 CONTROL
Description
The CONTROL method is run through when the current control has changed for an opened
screen, i.e. typically at a 1:n switchover.
Programming
Syntax: CONTROL
<instructions>
END_CONTROL
Description: Control switchover
Parameters: - None -
See also
Variable S_CONTROL (Page 91)
6.2.5 FOCUS
Description
The FOCUS method is executed if the focus (cursor) is positioned on another field in the dialog.
The FOCUS method must not be initiated as a result of a navigation event. The cursor position
may only be changed in softkey PRESS methods, CHANGE methods, etc. The response of
cursor movements is predefined.
Note
Within the FOCUS method, it is not possible to select a different variable, nor can a new dialog
be loaded.
Programming
Syntax: FOCUS
...
END_FOCUS
Description: Positions the cursor
Parameters: - None -
Example
FOCUS
DLGL("The focus has been placed on variable << FOC << ".)
END_FOCUS
See also
FOC variable (Page 89)
6.2.6 LANGUAGE
Description
The LANGUAGE method is run through when the current language has changed for an opened
screen.
Programming
Syntax: LANGUAGE
<instructions>
END_LANGUAGE
Description: Language
Parameters: - None -
See also
Variable S_LANG (Page 91)
6.2.7 LOAD
Description
The LOAD method is executed after the variable and softkey definitions (DEF Var1= ...,
HS1= ...) have been interpreted. At this time, the dialog is not yet displayed.
Programming
Syntax: LOAD
...
END_LOAD
Description: Download
Parameters: - None -
Example
Screen form1.Hd = $85111 ; Assign text for dialog header from language file
VAR1.Min = 0 ; Assign MIN variable limit
VAR1.Max = 1000 ; Assign MAX variable limit
END_LOAD ; End code
See also
Line, dividing line, rectangle, circle and ellipse (Page 167)
6.2.8 UNLOAD
Description
The UNLOAD method is executed before a dialog is unloaded.
Programming
Syntax: UNLOAD
...
END_UNLOAD
Description: Unload
Parameters: - None -
Example
UNLOAD
REG[1] = VAR1 ; Save variable in register
END_UNLOAD
6.2.9 OUTPUT
Description
The OUTPUT method is executed if the "GC" function is called. Variables and Help variables
are configured as an NC code in an OUTPUT method. The individual elements in a code line
are linked by means of blanks.
Note
The NC code can be generated in an extra file by means of file functions and transferred to
the NC.
Programming
Condition Response
Number of blocks remains unchanged. Block numbers are retained.
Number of blocks is reduced. The highest block numbers are canceled.
Number of blocks is increased. New blocks are not numbered.
Example
OUTPUT(CODE1)
"CYCLE82(" Var1.val "," Var2.val "," Var3.val ","Var4.val "," Var5.val ","
Var6.val ")"
END_OUTPUT
6.2.10 PRESS
Description
The PRESS method is executed when the corresponding softkey is pressed.
Programming
Syntax: PRESS(softkey)
...
END_PRESS
Designation: Pressing a softkey
Parameter: Softkey Name of softkey: HS1 - HS8 and VS1 - VS8
RECALL <RECALL> key
ENTER For the <ENTER> key, see PRESS(ENTER) (Page 108)
TOGGLE For the <TOGGLE> key, see PRESS(TOGGLE) (Page 108)
PU Page Up Screen up
PD Page Down Screen down
SL Scroll left Cursor left
SR Scroll right Cursor right
SU Scroll up Cursor up
SD Scroll down Cursor down
Example
6.2.11 PRESS(ENTER)
Description
The PRESS(ENTER) method is always called when the Enter key is pressed for a variable
with input/output field with input mode WR3 or WR5:
● WR3: Navigation to field and pressing of the Enter key
● WR5: In the input mode, transfer of the value with the Enter key
Programming
Syntax: PRESS(ENTER)
<instructions>
END_PRESS
Description: Enter key pressed
Parameters: - None -
6.2.12 PRESS(TOGGLE)
Description
The PRESS(TOGGLE) method is always called when the toggle key is pressed irrespective
of the currently focused variable.
When required, the FOC screen property can be used to determine which variable is currently
in focus.
Programming
Syntax: PRESS(TOGGLE)
<instructions>
END_PRESS
Description: Toggle key pressed
Parameter: - None -
Example
PRESS(TOGGLE)
DLGL("Toggle key pressed at variable " << FOC) ; The FOC screen property determines which
variable is currently in focus
END_PRESS
6.2.13 RESOLUTION
Description
The RESOLUTION method is run through when the current resolution has changed for an
opened screen, i.e. typically at a TCU switchover.
Programming
Syntax: RESOLUTION
<instructions>
END_RESOLUTION
Description: Resolution
Parameters: - None -
See also
Variables S_RESX and S_RESY (Page 92)
6.2.14 RESUME
Description
The RESUME method is called when the screen was interrupted, e.g. for an area change, and
is now shown again. The value changes are processed again, if required, the timers started
and the RESUME block executed.
Programming
Syntax: RESUME
<instruction>
END_RESUME
Description: Screen active again
Parameters: - None -
6.2.15 SUSPEND
Description
The SUSPEND method is called when the screen is interrupted and not unloaded. This is the
case, for example, when the screen is exited by a simple area change, but not explicitly
unloaded. The screen is retained in the background, but no value change or timers are
processed. The screen is paused.
Programming
Syntax: SUSPEND
<instruction>
END_SUSPEND
Description: Interruption of the screen
Parameters: - None -
Example
SUSPEND
MyVar1 = MyVar1 + 1
END_SUSPEND
Overview
Additional variables can be added to existing dialogs when expanding the user interface. A
version identifier in parentheses is appended to the additional variables in the definition
following the variable name: (0 = Original, is not written), 1 = Version 1, 2 = Version 2, etc.
Example:
When writing the OUTPUT method, you can specify which variables are written, with reference
to a particular version identifier.
Example:
The OUTPUT method for the original does not need a version identifier, however you can
specify it with 0. OUTPUT(NC1) is equivalent to OUTPUT(NC1,0). Version identifier n in the
OUTPUT method includes all variables of the originals 0, 1, 2, ... up to and including n.
OUTPUT(NC1)
var100",,"var101
END_OUTPUT
OUTPUT(NC1,1) Version 1
var100","var101"," var102
END_OUTPUT
6.3 Functions
Overview
A variety of functions are available in dialogs and dialog-dependent softkey menus. These can
be activated by specific events (exit input field, actuate softkey) and configured in methods.
Subprograms
Repeatedly used configuring instructions or others, which define the process for a particular
operation can be configured in subprograms. Subprograms can be loaded into the main
program or other subprograms at any time and executed as often as necessary, i.e. the
instructions they contain do not need to be configured repeatedly. The definition blocks of the
dialogs/softkey menu constitute a main program.
External functions
Additional, user-specific functions can be integrated by means of external functions. The
external functions are stored in a DLL file and identified by an entry in the definition lines of
the configuration file.
PI services
The PI_START function starts PI Services (Program Invocation Services) from the PLC in the
NC area.
See also
Function (FCT) (Page 131)
PI services (Page 145)
Description
You can read and write drive parameters using RDOP, WDOP and MRDOP functions.
Note
Do not read drive parameters faster than in a 1 second cycle, slower is better.
Reason: The communication with the drives can otherwise be extremely disturbed or even
cause failures.
Note
If errors occur when reading and writing drive parameters, the screen property ERR is set
appropriately.
Programming
Parameter: Identifier of the drive object The identifier of the drive object
can be taken, for example, from
the root screen of the "Setup" op‐
erating area.
Parameter number1 ... n In the variable names, "*" is the
separator. The values are trans‐
ferred to register REG[Register
index] in the order that the varia‐
ble names appear
in the command.
Register index The value of the first variable is
located in REG[Register index].
The value of the second variable
is located in REG[Register index
+ 1]
Examples
Read motor temperature r0035 of drive object "SERVO_3.3:2":
MyVar=RDOP("SERVO_3.3:2","35") ;
Read motor temperature r0035 and actual torque value r0080 of drive object "SERVO_3.3:2"
and store the respective results as of register index 10:
MRDOP("SERVO_3.3:2","35*80",10)
Description
The CALL function calls a loaded subprogram from any point in a method. Subprogram nesting
is supported, i.e. you can call a subprogram from another subprogram.
Programming
Syntax: CALL("Identifier")
Description: Subprogram call
Parameter: Identifier Name of subprogram
Example
//M(SCREEN FORM1)
DEF VAR1 = ...
DEF VAR2 = ...
CHANGE(VAR1)
...
CALL("MY_UP1") ; Call subprogram and execute
...
END_CHANGE
CHANGE(VAR2)
...
CALL("MY_UP1") ; Call subprogram and execute
...
END_CHANGE
SUB(MY_UP1)
;Do something
END_SUB
//END
Description
In the program file, subprograms are identified by the block identifier //B and terminated with //
END. Several subprograms can be defined under each block identifier.
Note
The variables used in the subprogram must be defined in the dialog in which the subprogram
is called.
Programming
A block is structured in the following way:
Example
Description
You can use the CVAR (CheckVariable) function to run a scan to ascertain whether all or only
certain variables or Help variables in a screen form are error-free.
It may be useful to check if variables contain a valid value before an NC code with the GC
function.
A variable is error-free if the state of the variable Identifier.vld = 1.
Programming
Syntax: CVAR(VarN)
Description: Checks variables for valid content
Parameters: VarN List of variables to be checked.
Up to 29 variables, each separated by a comma, can be
checked. A character length of 500 must not be exceeded.
The result of the scan can be:
1 = TRUE (all variables have valid content)
0 = FALSE (at least one variable has invalid content)
Example
6.3.5 CLEAR_BACKGROUND
Description
The CLEAR_BACKGROUND function deletes the LINE, RECT, ELLIPSE, V_SEPARATOR
and H_SEPARATOR graphic elements.
See also
Line, dividing line, rectangle, circle and ellipse (Page 167)
Description
The CP (Copy Program) function copies files within the HMI file system or within the NC file
system.
Programming
The return value (VAR1 defined as help variable) queries whether the function was successful:
CP("//NC/MPF.DIR/HOHO.MPF","//NC/MPF.DIR/ASLAN.MPF",VAR1)
Example
Application with return value:
CP("//NC/MPF.DIR/HOHO.MPF","//NC/MPF.DIR/ASLAN.MPF",VAR1)
CP("CF_CARD:/wks.dir/MESS_BILD.WPD/MESS_BILD.MPF","//NC/WKS.DIR/AAA.WPD/HOHO2.MPF",VAR1)
CP("//NC/MPF.DIR/HOHO.MPF","//NC/MPF.DIR/ASLAN.MPF") ; WPD must exist
CP("//NC/MPF.DIR/HOHO.MPF","//NC/MPF.DIR/ASLAN.MPF")
CP("CF_CARD:/mpf.dir/MYPROG.MPF","//NC/MPF.DIR/HOHO.MPF")
CP("//NC/MPF.DIR/HOHO.MPF","CF_CARD:/XYZ/MYPROG.MPF") ; XYZ must exist
See also
Support of FILE_ERR: FILE_ERR variable (Page 87)
Description
The DP (Delete Program) function deletes a file from the passive HMI or active NC file system.
Programming
Syntax: DP("File")
Description: Delete file
Parameter: File Complete path name of file to be deleted
Example
The following data management syntax is used for this function:
Description
The EP (Exist Program) function checks whether a particular NC program is stored on the
specified path in the NC or HMI file system.
Programming
Syntax: EP("File")
Description: Checks the existence of the NC program
Parameter: File Complete path to the file in the NC or HMI file system
Return value: Name of a variable to which the result of the scan should be assigned
The EP function can handle the new syntax and the old logic (with adapted syntax).
The file is directly addressed using a qualifying name:
//NC/MPF.DIR/XYZ.MPF
or
CF_CARD: /MPF.DIR/XYZ.MPF (points to /user/sinumerik/data/prog)
or
LOC: (corresponds to CF_CARD)
EP("//NC/WKS.DIR/TEST.WPD/XYZ.MPF",VAR1)
EP("CF_CARD:/mpf.dir/XYZ.MPF",VAR1)
EP("LOC:/mpf.dir/XYZ.MPF",VAR1)
; With return value:
; VAR1 = 0 File exists.
; VAR1 = 1 File does not exist.
EP("/MPF.DIR/CFI.MPF", VAR1)
; With return value:
; VAR1 = M File is located in the HMI file system.
; VAR1 = N File is located in the NC file system.
; VAR1 = B File is located in the HMI and the NC file system.
Example
IF VAR1 == "M"
DLGL("File is located in the HMI file system")
ELSE
IF VAR1 == "N"
DLGL("File is located in the NC file directory")
ELSE
DLGL("File is located neither in the HMI nor in the NC
file system")
ENDIF
ENDIF
Description
The MP (Move Program) function copies files within the HMI file system or within the NC file
system.
Programming
Examples
With return value:
MP("//NC/MPF.DIR/123.MPF","//NC/MPF.DIR/ASLAN.MPF",VAR1) ;Within NC
MP("//NC/MPF.DIR/123.MPF",VAR0,VAR1) ;Target via variable
MP(VAR4,VAR0,VAR1) ;Source and target via variable
MP("CF_CARD:/mpf.dir/myprog.mpf","//NC/MPF.DIR/123.MPF",VAR1) ;From CF card to NC
MP("//NC/MPF.DIR/HOHO.MPF","CF_CARD:/XYZ/123.mpf",VAR1) ;From NC to CF card
Description
The SP (Select Program) function selects a file in the active NC file system for execution, i.e.
the file must be loaded into the NC beforehand.
Programming
Syntax: SP("File")
Designation: Select program
Parameter: "File" Complete path name of NC file
Example
The following data management syntax is used for this function:
Description
The RDFILE and WRFILE functions are available for read and write access to files with INI
syntax.
The RDLINEFILE and WRLINEFILE functions are available for read and write access to
individual lines of a file.
Programming
Note
● The files must not be in the file system of the NC (data management).
● If the file does not exist, or the end of the file is reached or other errors occur, the variables
FILE_ERR and ERR are set accordingly. You can check whether a file exists first with the
Exist Program (EP) file function.
● The processed file is generated in "UTF-8" coding (without BOM (Byte Order Mask). When
reading a file, it is expected in "UTF-8" coding.
● You can delete the file explicitly when required with the Delete Program (DP) file function.
Examples
Result:
MyVar now contains the value "Daniel".
Result:
Content of file C:/tmp/myfile.ini:
<…>
[MySession]
NrOfSessions=12
<…>
MyVar = RDLINEFILE("C:/tmp/myfile.mpf", 4)
Result:
MyVar now contains the value " R[0]=R[0]+1"
WRLINEFILE("F100 X" << VARX << " Y" << VARY, "C:/tmp/mypp.mpf")
Result:
Content of c:/tmp/mypp.mpf:
<…>
F100 X123 Y456
Description
It is possible to configure short texts (messages or input tips) for output in the dialog line of the
dialog in response to certain situations.
Possible number of characters in the default font size: approx. 50
Programming
Syntax: DLGL("String")
Description: Outputs text in the dialog line
Parameter: String Text, which is displayed in the dialog line
Example
6.3.13 DEBUG
Description
The DEBUG function provides an analysis help during the draft phase of Run MyScreen user
screens. An expression in brackets transferred with the DEBUG function is evaluated during
runtime. The result is attached to the "easyscreen_log.txt" logbook as a separate entry.
Each entry has the current time stamp in square brackets as prefix (see example below).
It is recommended that the DEBUG outputs are removed in time-critical parts when possible.
Particularly after completing the draft phase, it is recommended that you comment out the
DEBUG outputs. The write access to the constantly expanding "easyscreen_log.txt" logbook
may slow down the processing.
Programming
Syntax: DEBUG(expression))
Description: Makes an entry in the "easyscreen_log.txt" logbook
Parameter: Expression to be evaluated from which an entry is generated in the logbook
Example
Description
The EXIT function is used to exit a dialog and return to the master dialog. If no master dialog
is found, you will exit the newly configured user interfaces and return to the standard application.
Syntax: EXIT
Description: Exits a dialog
Parameters: - None -
Example
PRESS(HS1)
EXIT
END_PRESS
Description
If the current dialog has been called with a transfer variable, the value of the variables can be
changed and transferred to the output dialog.
The variable values are each assigned to the variables transferred from the output dialog to
the subsequent dialog using the "LM" function. Up to 20 variable values, each separated by a
comma, can be transferred.
Note
The sequence of variables or variable values must be the same as the sequence of transfer
values programmed for the LM function to preclude assignment errors. Any unspecified
variable values will not be changed when the transfer is made. The modified transfer variables
are immediately valid in the output dialog on execution of the LM function.
Syntax: EXIT[(VARx)]
Description: Exits the dialog and transfers one or more variables
Parameters: VARx Label variables
Example
//M(Screen form1)
...
PRESS(HS1)
LM("SCREEN FORM2","CFI.COM",1, POSX,
POSY, DIAMETER)
; Interrupt screen form1 and open screen
form2. In doing this, transfer variables
POSX, POSY and DIAMETER.
DLGL("Screen form2 ended") ; After returning from screen form2, the
following text appears in the dialog line
of screen form1: Screen form2 ended.
END_PRESS
...
//END
//M(Screen form2)
...
PRESS(HS1)
EXIT(5, , CALCULATED_DIAMETER)
; Exit screen form2 and return to screen
form1 in the line after LM. In doing
this, assign the value 5 to the variable
POSX and the value of the CALCULATED_DI-
AMETER variable to the DIAMETER variable.
The variable POSY retains its current val-
ue.
END_PRESS
...
//END
6.3.15 Dynamic manipulation of the lists of toggle fields or list box fields
Description
The LISTADDITEM, LISTINSERTITEM, LISTDELETEITEM and LISTCLEAR functions are
used for the dynamic manipulation of the lists of toggle fields or list box fields.
These functions only have an effect on variables that have their own list, such as:
● "Simple" list
DEF VAR_AC1 = (I/* 0,1,2,3,4,5,6,7,8) or
● "Extended" list
DEF VAR_AC2 = (I/* 0="AC0", 1="AC1", 2="AC2", 3="AC3", 4="AC4",
5="AC5", 6="AC6", 7="AC7", 8="AC8").
If the variable points to an array, e.g. DEF VAR_AC3 = (I/* MYARRAY), these functions
are not available as otherwise the global array would be changed.
At least one value must be defined for the variable in the DEF line. This specifies the "Simple"
or "Extended" list type.
However, the list can then be completely deleted and, if required, completely rebuilt. The
"Simple" or "Extended" type must be retained however, it cannot be changed dynamically.
Programming
Examples
Note
The following examples build upon each other. The sequence of the examples is relevant in
order to understand the respective results.
Requirement/assumption:
DEF VAR_AC = (I/* 0="Off",1="On"/1/,"Switch"/WR2)
Result: REG[10] = 4
Description
The EVAL function evaluates a transferred expression and then executes it. With this function,
expressions can be programmed during runtime. This can be useful, for example, for indexed
access operations to variables.
Programming
Syntax: EVAL(exp)
Description: Evaluates an expression
Parameters: exp Logic expression
Example
VAR1=(S)
VAR2=(S)
VAR3=(S)
VAR4=(S)
CHANGE()
REG[7] = EVAL("VAR"<<REG[5]) ; The expression in parentheses produces VAR3 if the
value of REG[5] is equal to 3. The value of VAR3 is,
therefore, assigned to REG[7].
IF REG[5] == 1
REG[7] = VAR1
ELSE
IF REG[5] == 2
REG[7] = VAR2
ELSE
IF REG[5] == 3
REG[7] = VAR3
ELSE
IF REG[5] == 4
REG[7] = VAR4
ENDIF
ENDIF
ENDIF
ENDIF
END_CHANGE
Description
You can use the EXITLS function to exit the current user interface and load a defined softkey
menu.
Programming
Example
PRESS(HS1)
EXITLS( "Menu1", "AEDITOR.COM" )
END_PRESS
Description
The external functions are stored in a DLL file and identified by an entry in the definition lines
of the configuration file.
Note
The external function must have at least one return parameter.
Programming
The external function can, for example, be called from the LOAD method or executed in the
PRESS method.
Example:
press(vs4)
RET = InitConnection(VAR1,13,"Servus",VAR2,VAR17)
end_press
union CFI_VARIANT
(
char b;
short int i;
double r;
char* s;
)
typedef struct ExtFctStructTag
(
char cTyp;
union CFI_VARIANT value;
)ExtFctStruct;
typedef struct ExtFct* ExtFctStructPtr;
If the external function is to be developed independently of the platform (Windows, Linux), then
it is not permissible to use the keyword __declspec(dllexport). This keyword is only required
under Windows. For instance, the following macro can be used under Qt:
#ifdef Q_WS_WIN
#define MY_EXPORT __declspec(dllexport)
#else
#define MY_EXPORT
#endif
Description
The GC (Generate Code) function generates NC code from the OUTPUT method.
Programming
Parameter: Identifier Name of the OUTPUT method from which code is generated
Target file Path name of target file for HMI or NC file system
If the target file is not specified (only possible within Program‐
ming Support), the code will be written to the location of the
cursor within the file that is currently open.
Opt Option for generating comments.
0: (Default setting) Generate code with comment for the purpose
of recompilability (see also Recompile (Page 150)).
1: Do not create comments in the generated code.
Note: This code cannot be recompiled (see also Auto-Hot‐
spot).
Append This parameter is only relevant if a target file is specified.
0: (Default setting) If the file already exists, the old content is
deleted.
1: If the file already exists, the new code is written at the start of
the file.
2: If the file already exists, the new code is written at the end of
the file.
Example
//M(TestGC/"Code generation:")
DEF VAR1 = (R//1)
DEF VAR2 = (R//2)
DEF D_NAME
LOAD
VAR1 = 123
VAR2 = -6
END_LOAD
OUTPUT(CODE1)
"Cycle123(" VAR1 "," VAR2 ")"
"M30"
END_OUTPUT
PRESS(VS1)
D_NAME = "\MPF.DIR\MESSEN.MPF"
GC("CODE1",D_NAME) ; Write NC code from the OUTPUT method to file
\MPF.DIR\MESSEN.MPF:
Cycle123(123, -6)
M30
END_PRESS
Recompile
● No entry for target file:
The GC function can only be used in the Programming Support and writes the NC code to
the file currently open in the editor. Recompilation of the NC code is possible. If the GC
function is configured without a target file being specified under "Run MyScreens", an error
message is output when it is executed.
● Entry for target file:
The code generated from the OUTPUT method is entered in the target file. If the target file
does not already exist, it is set up in the NC file system. If the target file is stored in the HMI
file system, it is stored on the hard disk. User comment lines (information required to
recompile code) are not set up, i.e. the code cannot be recompiled.
Overview
The following password functions are available:
● Set password
● Delete password
● Change password
Syntax: HMI_LOGIN(Passwd)
Description: A password which sets the current access level is sent to the NCK with the
HMI_LOGIN() function.
Parameters: Passwd Password
Example
Syntax: HMI_LOGOFF
Description: The actual access level can be reset using the HMI_LOGOFF function.
Parameters: - None -
Example
Example
Description
The LA (Load Array) function can be used to load an array from another file.
Programming
Note
If an array in the current configuration file must be replaced by an array from another
configuration file, then both arrays must have the same name.
Example
Note
Please note that a valid value must be assigned to a variable after the LA function has been
used to assign another array to the toggle field of the variable.
Description
The LB (Load Block) function can be used to load blocks containing subprograms during
runtime. LB should be configured in a LOAD method so that the loaded subprograms can be
called at any time.
Note
Subprograms can also be defined directly in a dialog so that they do not have to be loaded.
Programming
Example
LOAD
LB("PROG1") ; Block "PROG1" is searched for in the current configura-
tion file and then loaded.
LB("PROG2","XY.COM") ; Block "PROG2" is searched for in the configuration file
XY.COM and then loaded.
END_LOAD
Description
The LM function loads a new dialog. Depending on the mode of the dialog change (see table
below), a message dialog can also be implemented with this function.
Programming
Note
Parameter VARx transfers only the value of the variable in each case, i.e. variables can be
read and written in the sub-dialog, but are not visible in it. Variables can be returned from the
sub-dialog to the master dialog by means of the EXIT function.
Example
SCREEN FORM1 (master dialog): Jump to the sub-dialog SCREEN FORM2 with variable
transfer
PRESS(HS1)
SCREEN FORM2 (sub-dialog): Return to master dialog SCREEN FORM1 with transfer of the
variable contents
PRESS(VS8)
Description
The LS function can be used to display another softkey menu.
Programming
Example
PRESS(HS4)
LS("Menu2",,0) ; Menu2 overwrites the existing softkey menu, the softkeys
that are displayed are deleted.
END_PRESS
Note
As long as the Interpreter has not displayed a dialog, i.e. no LM function has yet been
processed, only one LS or one LM command, but no other action, can be configured in the
PRESS method of the definition block for the start softkey and the softkey menu.
The LS and LM functions may only be called within a softkey PRESS method and will not react
if navigation keys are pressed (PU, PD, SL, SR, SU, SD).
Description
The table description (grid) can be dynamically provided within methods (e.g. LOAD) using
the LG method.
In order to assign a table using the LG method, the variable must have already been defined
as a grid variable and cross-referenced to an existing, valid table.
Programming
Example
Content of mygrids.com:
//G(MyGrid1/0/5)
(I///,"MyGrid1"/wr1//"1"/80/1)
(R3///"LongText1","R1-R4"/wr2//"$R[1]"/80/1)
(IBB///"LongText2","M2.2-M2.5"/wr2//"M2.2"/80/,1)
(R3///"LongText3","R9,R11,R13,R15"/wr2//"$R[9]"/110/2)
//END
Description
You can check a variable for different values with a SWITCH command.
The expression configured in the SWITCH statement is compared in succession to all the
values configured in the following CASE statements.
If not the same, a comparison is made with the following CASE statement. If a DEFAULT
statement follows and up to now no CASE statement was the same as the expression
configured in the SWITCH statement, the statements following the DEFAULT statement are
executed.
If the same, the following statements are executed until a CASE, DEFAULT or END_SWITCH
statement occurs.
Example
FOCUS
SWITCH (FOC)
CASE "VarF"
DLGL("Variable ""VarF"" has the input focus.")
CASE "VarZ"
DLGL("Variable ""VarZ"" has the input focus.")
DEFAULT
DLGL("Any other variable has the input focus.")
END_SWITCH
END_FOCUS
Description
This MRNP command transfers several NC/PLC variables in a single register access. This
access method is significantly faster than reading via individual access attempts. The NC/PLC
variables must be included within an MRNP command of the same area.
The areas of the NC/PLC variables are organized as follows:
● General NC data ($MN..., $SN.., /nck/...)
● Channel-specific NC data ($MC..., $SC.., /channel/...)
● PLC data (DB..., MB.., /plc/...)
● Axis-specific NC data on the same axis ($MA..., $SA..)
Programming
Note
It should be noted that the number of registers is restricted and the list of variables cannot
exceed 500 characters.
Example
NC variable
All machine data, setting data and R parameters are available, but only certain system
variables (see also: List of accessible system variables (Page 240)).
All global and channel-specific user variables (GUDs) can be accessed. However, local and
program-global user variables cannot be processed.
Machine data
Global machine data $MN_...
Axis-specific machine data $MA_...
Channel-specific machine data $MC_...
Setting data
Global setting data $SN_...
Axis-specific setting data $SA_...
Channel-specific setting data $SC_...
System variables
R parameter 1 $R[1]
PLC variable
All PLC data are available.
PLC data
Byte y bit z of data block x DBx.DBXy.z
Byte y of data block x DBx.DBBy
Word y of data block x DBx.DBWy
Double word y v. of data block x DBx.DBDy
Real y of data block x DBx.DBRy
Flag byte x bit y Mx.y
PLC data
Flag byte x MBx
Flag word x MWx
Flag double word x MDx
Input byte x bit y Ix.y or Ex.y
Input byte x IBx or EBx
Input word x IWx or EWx
Input double word x IDx or EDx
Output byte x bit y Qx.y or Ax.y
Output byte x QBx or ABx
Output word x QWx or AWx
Output double word x QDx or ADx
String y with length z from data block x DBx.DBSy.z
6.3.28 PI services
Description
The PI_START function starts PI Services (Program Invocation Services) from the PLC in the
NC area.
Note
A list of the available PI services can be found in the Basic Functions Function Manual.
Programming
Example
PI_START("/NC,001,_N_LOGOUT")
Note
Channel-dependent PI Services always refer to the current channel.
PI services of the tool functions (TO area) always refer to the TO area that is assigned to the
current channel.
Description
The RNP (Read NC PLC) command can be used to read NC or PLC variables or machine
data.
Programming
Example
Description
The WNP (Write NC PLC) command can be used to write NC or PLC variables or machine
data.
NC/PLC variables are accessed anew every time the WNP function is executed, i.e., NC/PLC
access is always executed in a CHANGE method. It is advisable to use this option in cases
where a system or user variable changes value frequently. If an NC/PLC variable is to be
accessed only once, then it must be configured in a LOAD or UNLOAD method.
Programming
Example
Description
The RESIZE_VAR_IO() and RESIZE_VAR_TXT() commands changes the geometry of
the input/output component or text component of a variable.
After setting the new geometry, all fields of the screen are positioned as if the screen had been
configured with these positions from the start. In this way, all fields are correctly aligned,
depending on the configuration.
Programming
Note
The previous value is retained for each value of X, Y, Width or Height that is not specified. If
-1 is specified for one of these values, "Run MyScreens" sets the specified component of the
default position.
Example
Register description
Registers are needed in order to exchange data between different dialogs. Registers are
assigned to each dialog. These are created when the first dialog is loaded and assigned the
value 0 or an empty string.
Note
Registers must not be used directly in an OUTPUT method for generating NC code.
Programming
Syntax: REG[x]
Description: Defines a register
Parameters: x Register index with x = 0...19;
Type: REAL or STRING = VARIANT
Registers with x ≥ 20 have already been assigned by Siemens.
Note
If a new dialog is generated from an existing dialog by means of the LM function, register
content is automatically transferred to the new dialog at the same time and is available for
further calculations in the second dialog.
Programming
Example
UNLOAD
REG[0] = VAR1 ; Assign value of variable 1 to register 0
END_UNLOAD
UNLOAD
REG[9].VAL = 84 ; Assign value 84 to register 9
END_UNLOAD
; These registers can then be assigned to local variables
again in a method in the next dialog.
LOAD
VAR2 = REG[0]
END_LOAD
Programming
Syntax: Identifier.vld
Description: The property is read-only property.
Parameters: Identifier Name of the register
Return value: The result of the scan can be:
FALSE = invalid value
TRUE = valid value
Example
6.3.32 RETURN
Description
The RETURN function can be used to prematurely terminate execution of the current
subprogram and to return to the branch point of the last CALL command.
If no RETURN command is configured in the subprogram, the subprogram will run to the end
before returning to the branch point.
Programming
Syntax: RETURN
Description: Returns to the branch point
Parameters: - None -
Example
6.3.33 Recompile
Description
In the programming support system, it is possible to recompile NC code that has been
generated with the GC function and to display the variable values in the input/output field of
the associated entry dialog again.
Programming
Variables from the NC code are transferred to the dialog. At the same time, the variable values
from the NC code are compared with the calculated variable values from the configuration file.
If the values do not coincide, an error message is written to the log book because values have
been changed during NC code generation.
If the NC code contains the same variable several times, it is evaluated at the point where it
last occurs during recompilation. A warning is also written to the log book.
Variables not utilized in NC code during code generation are stored as user comment. The
term "user comment" refers to all information required to recompile codes. User comment must
not be altered.
Note
The block consisting of NC code and user comment can be recompiled only if it starts at the
beginning of a line.
Examples:
The programm contains the following NC code:
DEF VAR1=(I//101)
OUTPUT(CODE1)
"X" VAR1 " Y200"
"X" VAR1 " Y0"
END_OUTPUT
;NCG#TestGC#\cus.dir\aeditor.com#CODE1#1#3#
X101 Y200
X101 Y0
;#END#
X101 Y200
X222 Y0 ; The value for X has been changed in the part program (X101 → X222)
The following value is displayed for VAR1 in the input dialog: VAR1 = 222
See also
Generate code (GC) (Page 133)
Description
In the Programming Support, it is possible to recompile without user comments the NC code
that has been generated with the GC function and to display the variable values in the input/
output field of the associated entry dialog again.
Programming
The GC command can be executed in the following way in order to suppress comment lines
that are generated for standard code generation:
GC("CODE1",D_NAME,1)
Normally, the resulting code cannot be recompiled. The following steps are required in order
to be able to recompile the cycle calls generated in this way:
● Expanding the easyscreen.ini
Section [RECOMPILE_INFO_FILES] will be introduced into the easyscreen.ini file. In this
section, all ini files are listed that contain descriptions for cycles recompiled without user
comment:
[RECOMPILE_INFO_FILES]
IniFile01 = cycles1.ini
IniFile02 = cycles2.ini
Several ini files can be specified, whose names can be freely selected.
● Creating an ini file for a cycle description
Save the ini file with the cycle descriptions under the following path:
[System user directory]/cfg
[System oem directory]/cfg
[System add_on directory]/cfg
A separate section is required for each cycle. The section name corresponds to the name
of the cycle:
[Cycle123]
Mname = TestGC
Dname = testgc.com
OUTPUT = Code1
Anzp = 3
Version = 0
Code_type = 1
Icon = cycle123.png
Desc_Text = This is describing text
Icon (optional) icon for display in the machining step program, format
*.png
Screen size for corresponding resolution:
640 X 480 mm → 16 x 16 pixels
800 X 600 mm → 20 x 20 pixels
1024 X 768 mm → 26 x 26 pixels
1280 X 1024 mm → 26 x 26 pixels
1280 X 768 mm → 26 x 26 pixels
Archive: [system user directory]/ico/ico<resolution>
Note: For resolutions of 1280, the folder for 1024 x 768 mm is used
(only suitable for machining step programs).
Desc_Text (optional) Explanation text for display in the machining step pro‐
gram, max. length of string is 17 characters (only suitable for ma‐
chining step programs).
Example
//M(TestGC/"Code generation:")
DEF VAR1 = (R//1)
DEF VAR2 = (R//2)
DEF D_NAME
LOAD
VAR1 = 123
VAR2 = -6
END_LOAD
OUTPUT(CODE1)
"Cycle123(" VAR1 "," VAR2 ")"
"M30"
END_OUTPUT
PRESS(VS1)
D_NAME = "\MPF.DIR\MESSEN.MPF"
GC("CODE1",D_NAME) ;Write NC code from the OUTPUT method to
file \MPF.DIR\MESSEN.MPF:
Cycle123(123, -6)
M30
END_PRESS
Supplementary conditions
● The "Recompile without user comment" functionality does not have the full range of
functions as "Recompile with user comment".
Typical cycle calls, such as MYCYCLE(PAR1, PAR2, PAR3, …), are supported during
"Recompile without user comment". However, there must not be a user comment in the
line of the function call. Optional parameters that are not transferred during the function call
are of the S type string; however, they must be at least specified using empty quotation
marks, e.g. "". Otherwise, "Run MyScreens" attempts to fill these parameters using commas
so that the "filled cycle call" can then be recompiled.
● Parameters of the string type must not have any commas or semicolons in the string to be
transferred.
● During "Recompile without user comment", all variables contained in the OUTPUT method
must always be within the brackets so that the "Fill in missing cycle parameters with
commas" functionality can take effect.
Example:
Permitted:
OUTPUT
"MYCYCLE(" MYPAR1 "," MYPAR2 "," MYPAR3 ")"
END_OUTPUT
OUTPUT
"MYCYCLE(" MYPAR1 "," MYPAR2 "," MYPAR3 ")" MYCOMMENT
END_OUTPUT
Description
The SF, SB (Search Forward, Search Backward) function is used to search for a string from
the current cursor position in the NC program currently selected in the Editor and to output its
value.
Programming
Syntax: SF("String")
Identifiers: Search Forward: Search forward from the current cursor position
Syntax: SB("String")
Identifiers: Search Backward: Search backward from the current cursor position
Parameters: String Text to be found
Example
The following notations are possible:
Overview
The following functions enable strings to be processed:
● Determine length of string
● Find a character in a string
● Extract substring from left
● Extract substring from right
● Extract substring from mid-string
● Replace substring
● Compare strings
● Insert a string in another string
● Remove a string from a string
Example
DEF VAR01
DEF VAR02
LOAD
VAR01="HALLO"
VAR02=LEN(VAR01) ; Result = 5
END_LOAD
Example
DEF VAR01
DEF VAR02
LOAD
VAR01="HALLO/WELT"
VAR02=INST(1,"/",VAR01) ; Result = 6
END_LOAD
Example
DEF VAR01
DEF VAR02
LOAD
VAR01="HALLO/WELT"
VAR02=LEFT(VAR01,5) ; Result = "HELLO"
END_LOAD
Example
DEF VAR01
DEF VAR02
LOAD
VAR01="HALLO/WELT"
VAR02=LEFT(VAR01,4) ; Result = "WORLD"
END_LOAD
Example
DEF VAR01
DEF VAR02
LOAD
VAR01="HALLO/WELT"
VAR02=LEFT(VAR01,4,4) ; Result = "LO/W"
END_LOAD
Example
Example
Example
Syntax: TRIMLEFT(string1)
Description: TRIMLEFT removes blanks on the left from a character string.
Parameters: string1 Character string from which blanks are to be removed
from the left of the character string
Example
Syntax: TRIMRIGHT(string1)
Description: TRIMLEFT removes blanks on the right from a character string.
Parameters: string1 Character string from which blanks are to be removed
from the right of the character string
Example
Example
DEF VAR1
DEF VAR2
LOAD
VAR1 = 123
VAR2 = FORMAT("Hello %08b %.2f %s!", VAR1 + 1, 987.654321, "world")
; Result = "Hello 01111100 987.65 world!"
END_LOAD
See also
Use of strings (Page 83)
Description
A loop can be implemented with the DO LOOP commands. Depending on the configuration,
it is run through as long as a condition is satisfied (WHILE) or until a condition occurs (UNTIL).
As loops can impair the system performance, depending on the configuration, they should be
used carefully and without time-intensive actions in the loops.
It is recommended that a register (REG[]) be used as run variable, because normal display
variables (particularly those with system or user variables connection) also impair the system
performance due to the frequent updates or write operations.
The runtime of "Run MyScreens" methods can be determined with the DEBUG function (see
Section DEBUG (Page 125)). Problems caused by loops (high CPU load, reduced response
capability) may be identified in this way.
Note
As each FOR loop can be replaced by a WHILE loop, the syntax to formulate a FOR loop is
not supported in EasyScreen.
Programming
DO
<instructions>
LOOP_WHILE <Condition to continue the loop>
DO
<instructions>
LOOP_UNTIL <Condition to terminate the loop>
Example
REG[0] = 5
DO
DEBUG("OUTER: " << REG[0])
REG[0] = REG[0] + 1
REG[1] = -5
DO
DEBUG("INNER: " << REG[1])
REG[1] = REG[1] + 1
LOOP_WHILE REG[1] < 0
REG[0] = 5
DO
DEBUG("OUTER: " << REG[0])
REG[0] = REG[0] + 1
REG[1] = -5
DO
DEBUG("INNER: " << REG[1])
REG[1] = REG[1] + 1
LOOP_UNTIL 0 <= REG[1]
REG[0] = 5
DO_WHILE 10 > REG[0]
DEBUG("OUTER: " << REG[0])
REG[0] = REG[0] + 1
REG[1] = -5
LOOP
REG[0] = 5
DO_WHILE 10 > REG[0]
DEBUG("OUTER: " << REG[0])
REG[0] = REG[0] + 1
REG[1] = -5
DO
DEBUG("INNER: " << REG[1])
REG[1] = REG[1] + 1
LOOP_UNTIL 0 <= REG[1]
LOOP
Description
SUB methods can be called cyclically with the aid of timers. The START_TIMER() and
STOP_TIMER() functions are available for this purpose.
Note
Only one timer can be configured for each SUB method.
Programming
Example
//M(TimerSample/"My timer")
DEF MyVariable=(I//0/,"Number of cyclic calls:"/WR1)
VS1=("Start%ntimer")
VS2=("Stop%ntimer")
SUB(MyTimerSub)
MyVariable = MyVariable + 1
END_SUB
//M(TimerSample/"My timer")
PRESS(VS1)
;Calls SUB "MyTimerSub" every 1000 milliseconds
START_TIMER("MyTimerSub", 1000)
END_PRESS
PRESS(VS2)
STOP_TIMER("MyTimerSub")
END_PRESS
If START_TIMER is called again for a timer already assigned to a SUB method, then the new
interval is taken over if it is different. Otherwise, the second call is ignored.
The smallest interval for the system is100 milliseconds.
If STOP_TIMER is called for a SUB method for which no timer is currently running, the call is
ignored.
Description
Lines, dividing lines, rectangles and ellipses/circles are configured in the LOAD method:
● Transparent rectangles are created by setting the fill color to the system background color.
● With the ELLIPSE element, a circle is created by setting the height and the width to the
same value.
● Horizontal and vertical dividing lines always have the exact window width or window height.
No scrollbars are produced by dividing lines.
If you previously used the RECT element to display dividing lines, e.g.
RECT(305,0,1,370,0,0,1), this is detected by the Programming Support and automatically
converted to V_SEPARATOR(305,1,"#87a5cd", 1). This applies to both vertical and
horizontal dividing lines.
LINE element
Programming:
RECT element
Programming:
ELLIPSE element
Programming:
Syntax: ELLIPSE(x,y,w,h,f1,f2,s)
Description: Defines an ellipse or circle
Parameter: x x-coordinate, top left
y y-coordinate, top left
w Width
h Height
f1 Color of the border
f2 Fill color
s Border style:
1 = solid
2 = dashed
3 = dotted
4 = dashed and dotted
A circle is created when the values for height and width are the same.
V_SEPARATOR element
Programming:
H_SEPARATOR element
Programming:
See also
LOAD (Page 104)
See also
CLEAR_BACKGROUND (Page 117)
Definition
An array can be used to organize data of the same data type stored in the memory in such a
way that it is possible to access the data via an index.
Description
Arrays can be one- or two-dimensional. A one-dimensional array is treated like a two-
dimensional array with just one line or column.
Arrays have start identifier //A and end identifier //END. The number of lines and columns is
optional. An array is structured in the following way:
Programming
Syntax: //A(Identifier)
(a/b...)
(c/d...)
...
//END
Description: Defines array
Parameters: Identifier Name of array
a, b, c, d Values of array
Values of the STRING type must be enclosed in double quo‐
tation marks.
Example
Description
The value of an array access operation can be transferred with property Value (identifier.val).
The line index (line number of the array) and the column index (column number of the array)
each begin at 0. If a line index or column index is outside the array, the value 0 or a blank
string is output and the ERR variable is set to TRUE. Variable ERR is also set to TRUE if a
search concept cannot be found.
Programming
M: Access mode
0 Direct
1 Searches the line, column directly
2 Searches the column, line directly
3 Searches
4 Searches line index
5 Searches column index
C: Compare mode
0 Search concept must be located in the range of values
of the line or column.
1 Search concept must be located exactly.
Example:
VAR1 = MET_G[REG[3],1,0].VAL ;Assign Var1 a value from
array MET_G
Access mode
● "Direct" access mode
With "Direct" access mode (M = 0), the array is accessed with the line index in Z and the
column index in S. Compare mode C is not evaluated.
● "Search" access mode
In the case of access mode M = 1, 2 or 3, the search always commences in line 0 or column
0.
Compare mode
When compare mode C = 0 is used, the content of the search line or search column must be
sorted in ascending order. If the search concept is smaller than the first element or greater
than the last, the value 0 or a blank string is output and the error variable ERR is set to TRUE.
When compare mode C = 1 is used, the search concept must be present in the search line or
search column. If the search concept cannot be found, the value 0 or a blank string is output
and the error variable ERR is set to TRUE.
Prerequisite
Two arrays are defined below. These are the basis for the following examples:
//A(Thread)
(0.3 / 0.075 / 0.202)
(0.4 / 0.1 / 0.270)
(0.5 / 0.125 / 0.338)
(0.6 / 0.15 / 0.406)
(0.8 / 0.2 / 0.540)
(1.0 / 0.25 / 0.676)
(1.2 / 0.25 / 0.676)
(1.4 / 0.3 / 1.010)
(1.7 / 0.35 / 1.246)
//END
//A(Array2)
("DES" / "PTCH" / "CDM" )
(0.3 / 0.075 / 0.202 )
(0.4 / 0.1 / 0.270 )
(0.5 / 0.125 / 0.338 )
(0.6 / 0.15 / 0.406 )
(0.8 / 0.2 / 0.540 )
(1.0 / 0.25 / 0.676 )
(1.2 / 0.25 / 0.676 )
Examples
● Access mode example 1:
The search concept is in Z. This key is always sought in column 0. The value from column
S is output with the line index of the concept found.
VAR1 = Thread[0.5,1,1] ;VAR1 has the value 0.125
Explanation:
Search for value 0.5 in column 0 of "Thread" array and output the value found in column 1
of the same line.
● Access mode example 2:
The search concept is in S. This concept is always searched for in line 0. The value from
line Z is output with the column index of the concept found:
VAR1 = ARRAY2[3,"PTCH",2] ;VAR1 has the value 0.125
Explanation:
Search for column containing "PTCH" in line 0 of array "Array2". Output the value from the
column found and the line with index 3.
● Access mode example 3:
A search concept is in each of Z and S. The line index is searched for in column 0 with the
concept in Z and the column index in line 0 with the concept in S. The value from the array
is output with the line index and column index found:
VAR1 = ARRAY2[0.6,"PTCH",3] ;VAR1 has the value 0.15
Explanation:
Search for the line with the content 0.6 in column 0 of array "Array2", search for the column
with the content "STG" in line 0 of Array2. Transfer the value from the line and column found
to VAR1.
● Access mode example 4:
The search concept is in Z. S contains the column index of the column in which concept is
being searched for. The line index of the concept found is output:
VAR1 = Thread[0.125,1,4] ;VAR1 has the value 2
Explanation:
Search for value 0.125 in column 1 of array "Thread" and transfer the line index of the value
found to VAR1.
● Access mode example 5:
Z contains the line index of line in which concept is being searched for. The search concept
is in S. The column index of the concept found is output:
VAR1 = Thread[4,0.2,5,1] ;VAR1 has the value 1
Explanation:
Search in line 4 of the "Thread" array for the value 0.2 and transfer the column index of the
value found to VAR1. Comparison mode 1 was selected because the values of line 4 are
not sorted in ascending order.
Description
The Status property can be used to run a scan to find out whether an array access operation
is supplying a valid value.
Programming
Example
Definition
In contrast to the array, the values of a table (grid) are continually updated. It is a tabular display
of values that can come from the NC or PLC. The table is organized in columns and always
has variables of the same type in one column.
Assignment
The reference to a table description is performed in the variables definition:
● The variables definition determines the values to be displayed, and the definition of table
elements determines the appearance and arrangement on the screen window. The
properties of the input/output fields from the definition line of the variables are taken over
in the table.
● The visible area of the table is determined by the width and height of the input/output field.
Any lines or columns than cannot be seen can be displayed by scrolling horizontally and
vertically.
Table identifiers
Identifiers of a table containing NCK or PLC values of the same type, which can be addressed
via a channel block. The table identifier is differentiated from limits or toggle fields by the
addition of a % sign in front of it. The file containing the table description can be specified by
adding a comma after the identifier and then inserting the name of the file.
Identifier of a table for values of the same type, e.g. from the NCK or PLC. The table identifier
is specified at the position at which the limit values or the toggle field are configured. The table
identifier starts with a leading % character. This can be followed by a file name with a comma
as separator. It specifies the file in which the table description is defined. Per default, the table
is sought in the configuration file in which the screen is configured.
A table definition can also be loaded dynamically, e.g. in the LOAD method via the Load Grid
(LG) function.
Example
Definition of a MyGridVar variable which displays a "MyGrid1" grid in its input/output field
(distance from left: 100, distance from top: Standard, width: 350, height: 100).
DEF MyGridVar=(V/% MyGrid1///////100,,350,100)
See also
Parameters of variables (Page 71)
Load Grid (LG) (Page 141)
Description
The table block comprises:
● Header
● 1 to n column descriptions
Programming
Examples
Description
For tables (grids), it is advisable to use variables with an index. For PLC or NC variables, the
index number with one or more indices is of significance.
The values displayed in a table can be modified directly within the restrictions of the rights
granted by the attributes and within any defined limits.
Programming
See also
Load Grid (LG) (Page 141)
Description
The Row and Col properties can be used to set and calculate the focus within a table:
● Identifier.Row
● Identifier.Col
Programming
Each cell in a table has the Val and Vld properties.
In order to read and write cell properties, a line and column index must be specified in addition
to the variable identifiers from the definition list.
Example
Var1[2,3].val=1.203
If the line and column indices are not specified, the indices of the focused cell apply. This
corresponds to:
Var1.Row =2
Var1.Col=3
Var1.val=1.203
Description
User-specific display elements are configured in the dialog using a custom widget.
Software option
In order to use custom widgets in dialog boxes, you require the following additional
software option:
"SINUMERIK Integrate Run MyHMI /3GL" (6FC5800-0AP60-0YB0)
Programming
Example
A custom widget is defined in the dialog configuration in the following way:
DEF Cus = (W///"","slestestcustomwidget.SlEsTestCustomWidget"/////
20,20,250,100);
Description
Essentially, the custom widget library contains a defined class. The name of this class must
be specified in the dialog configuration in addition to the library names. Starting from library
names, "Run MyScreens" accesses a dll file with the same name, e.g.:
slestestcustomwidget.dll
Programming
The class definition of the dll file should look like this:
Description
The library is supplemented by an interface in order to display the custom widget in the dialog.
This contains macro definitions with which "Run MyScreens" initiates the custom widget. The
interface is available in the form of a cpp file. The file name can be freely selected, e.g.:
sleswidgetfactory.cpp
Programming
The interface is defined as follows:
#include "slestestcustomwidget.h" ; The header file for the relevant custom widg-
ets is inserted at the beginning of the file
....
//Makros ; Macro definitions are not changed
....
WIDGET_CLASS_EXPORT(SlEsTestCustom- ; The relevant custom widget is declared at
Widget) the end of the file
Example
Content of the file sleswidgetfactory.cpp for a custom widget with the class name
SlEsTestCustomWidget":
#include <Qt/qglobal.h>
#include "slestestcustomwidget.h"
///////////////////////////////////////////////////////////////////////////
// MAKROS FOR PLUGIN DLL-EXPORT - DO NOT CHANGE
///////////////////////////////////////////////////////////////////////////
#ifndef Q_EXTERN_C
#ifdef __cplusplus
#define Q_EXTERN_C extern "C"
#else
#define Q_EXTERN_C extern
#endif
#endif
#ifdef Q_WS_WIN
# ifdef Q_CC_BOR
# define EXPORT_SL_ES_CUSTOM_WIDGET_PLUGIN(PLUGIN,PARAM) \
Q_EXTERN_C __declspec(dllexport) void* \
__stdcall SL_ES_FCT_NAME(PLUGIN) (QWidget* pParent) \
SL_ES_CUSTOM_WIDGET_PLUGIN_INSTANTIATE( PLUGIN,PARAM )
# else
# define EXPORT_SL_ES_CUSTOM_WIDGET_PLUGIN(PLUGIN,PARAM) \
Q_EXTERN_C __declspec(dllexport) void* SL_ES_FCT_NAME(PLUGIN) \
(QWidget* pParent) \
SL_ES_CUSTOM_WIDGET_PLUGIN_INSTANTIATE( PLUGIN,PARAM )
# endif
#else
# define EXPORT_SL_ES_CUSTOM_WIDGET_PLUGIN(PLUGIN,PARAM) \
Q_EXTERN_C void* SL_ES_FCT_NAME(PLUGIN) (QWidget* pParent) \
SL_ES_CUSTOM_WIDGET_PLUGIN_INSTANTIATE( PLUGIN,PARAM )
#endif
#define WIDGET_CLASS_EXPORT(CLASSNAME) \
EXPORT_SL_ES_CUSTOM_WIDGET_PLUGIN(CLASSNAME,CLASSNAME(pParent))
///////////////////////////////////////////////////////////////////////////
// FOR OEM USER - please declare here your widget classes for export
///////////////////////////////////////////////////////////////////////////
WIDGET_CLASS_EXPORT(SlEsTestCustomWidget)
7.4.4 Interaction between custom widget and dialog box - Automatic data exchange
Custom widgets interact with dialog boxes and can display values or manipulate them.
Conditions
Automatic data exchange takes place under the following conditions:
Condition Direction
When starting or recompiling a dialog Dialog → custom widget
When executing the GC command for generating cycle calls Custom widget → Dialog
Programming
The following definitions are necessary for the interaction:
Expansion of the dialog configuration
Example
DEF CUSVAR1 = (R//5/"","CUSVAR1",""/wr2/)
Example
The class definition of the dll file should look like this:
{
Q_OBJECT
Q_PROPERTY(double CUSVAR1 READ cusVar1 WRITE setCusVar1);
....
....
}
7.4.5 Interaction between custom widget and dialog box - Manual data exchange
Besides automatic data exchange, manual data exchange is also possible. Data exchange is
dynamic, i.e. takes place while the dialog box is running. The following actions are possible:
● Properties of the custom widget can be read and written.
● Methods of the custom widget can be called from the Run MyScreens configuration.
● A response to a particular signal of the custom widget can be implemented in order to call
subprograms (SUB) in the Run MyScreens configuration.
Description
The functions ReadCWProperties and WriteCWProperties are provided in the Run MyScreens
configuration for reading and writing properties of the custom widgets.
Programming
Syntax:
ReadCWProperty("Variablename", "Propertyname")
Syntax:
WriteCWProperty("Variablename", "Propertyname", "Value")
Parameters: Variable name Name of a dialog box variable to which a custom widget
is assigned
Propertyname Name of the custom widget property to be written
Value Value to be written to the property of the custom widget
Examples
Example 1:
Read property "MyStringVar" of the custom widget that is linked to dialog box variable
"MyCWVar1" and assign the value to register 7.
Example 2:
Write the result of the calculation "3 + sin(123.456)" into property "MyRealVar" of the custom
widget that is linked to dialog box variable "MyCWVar1."
Description
The function CallCWMethod is available in the Run MyScreens configuration for executing
methods of the custom widget.
The custom widget method to be called must have no more than 10 transfer parameters.
The following transfer parameter data formats are supported:
● bool
● uint
● int
● double
● QString
● QByteArray
Programming
Example
PRESS(VS3)
REG[9] = CallCWMethod("MyCWVar1", "myFunc1", 1+7, MyStringVar1, sin(MyRealVar) –
8)
END_PRESS
Note
The custom widget must implement the "serialize" method. Here, you have the option of writing
the internal data of a custom widget
to a specified file, or restoring it again. This is especially necessary, if, with the "Run
MyScreens" screen open, you change to another operating area and then return again.
Otherwise, internal data are lost when redisplaying.
Example
if (bIsStoring)
{
mode = QIODevice::WriteOnly;
}
else
{
mode = QIODevice::ReadOnly;
}
if (fileData.open(mode))
{
QDataStream streamData;
streamData.setDevice(&fileData);
if (bIsStoring)
{
streamData << m_nDataCount << m_dValueX;
}
else
{
streamData >> m_nDataCount >> m_dValueX;
}
streamData.setDevice(0);
fileData.flush();
fileData.close();
bReturn = true;
}
}
return bReturn;
}
Description
In Run MyScreens it is possible to respond to a particular signal (invokeSub()) of the custom
widget and call up a subprogram (SUB).
10 global variables, the so-called SIGARG, are available for passing values (custom widget
signal -> SUB), which are comparable to registers (REG) in configuration. This is where the
values transferred with the custom widget signal are stored.
Programming
Subroutine to be called:
Syntax: SUB(on_<Variablename>_<Signalname>)
…
END_SUB
Description: Response to a custom widget signal
Parameters: Variable name Name of a dialog box variable to which a custom widget
is assigned.
Signal name Name of the custom widget signal
SIGARG 0 - 9 Transfer parameters for the custom widget method.
Supported data formats: See above
Note: The transfer parameters are always passed "By‐
Val," i.e. only the value and not, for example, the refer‐
ence to a variable is passed.
Example
Topic, "Formatting error", Page 210, Chapter "Response to a Custom Widget signal", Section
"Example"
In this case, formatting/indentation is not correct. Correct would be:
QVariantList vntList;
vntList << 123.456;
emit invokeSub("MySub", vntList);
Result easyscreen_log.txt:
7.5 SIEsGraphCustomWidget
7.5.1 SIEsGraphCustomWidget
General
Using SlEsGraphCustomWidget, you can display geometrical objects (point, line, square,
square with rounded corners, ellipse, arc, text) and curves from interpolation points (e.g.
measured values, characteristic).
The objects are organized in one or several contours. These can then be displayed, either
individually or combined; they can also be entered, selected and deleted.
Using functions, the objects are added to the currently selected contour, and these are then
drawn in this particular sequence. If you wish to draw the object in a specific color, then you
must set the appropriate pen color before adding. All objects subsequently added will be drawn
in this pen color. In addition to the pen color, you can also influence the pen width and pen
style. For closed objects such as square, square with rounded edges and ellipse, before adding
the objects you can set a fill color.
Every contour can be brought into various modes:
● Standard display of all object types.
● Points can be connected to create a polyline, and can therefore be displayed as curve/graph.
● The area between points, lines or arcs up to the X axis can be filled in with the currently
selected fill color. For instance, you can use this option to visualize residual material when
turning.
If, in this mode, points are displayed in addition as polyline, then the complete area below
the curve up to the X axis is filled. The points, lines and arcs can be located in all four
quadrants.
You can move along one or several contours using a special cursor mode. To do this, the
cursor is set to the first or last point object of a contour or, starting from the actual cursor position
is moved either forward or backward within the contour of a point object.
When required, a second Y axis (right) can be displayed with its own scaling. This is coupled
to the first Y axis (left) through an offset and a factor.
Based on a specified X coordinate, using a search function, a point previously added to the
contour can be found, and if required, the cursor can be set to this point.
You can also configure contours as ring buffer with an adjustable size.
As a result of the serialization, the actual state of the SlEsGraphCustomWidget can be saved
in a file in binary form - and also restored.
The SlEsGraphCustomWidget can be operated using the "Pan" gesture (where the view is
shifted) and the "Pinch"/"Spread" gestures (zooming in and out of the view).
Using the mouse, you can shift the view (left mouse button + Move), and you can zoom in and
out (mouse wheel).
For performance reasons, the display is not automatically refreshed. Depending on the
particular application, you can initiate the refresh by calling the appropriate function.
Example
//M(MyGraphSampleMask/"SlEsGraphCustomWidget Sample")
DEF MyGraphVar = (W///,"slesgraphcustomwidget.SlEsGraphCustomWidget"/////10,10,340,340/0,0,0,0)
VS1=("Add objects",,se1)
LOAD
WRITECWPROPERTY("MyGraphVar", "AxisNameX", "X")
WRITECWPROPERTY("MyGraphVar", "AxisNameY", "Y")
WRITECWPROPERTY("MyGraphVar", "ScaleTextOrientationYAxis", 2)
WRITECWPROPERTY("MyGraphVar", "KeepAspectRatio", TRUE)
PRESS(VS1)
REG[0]= CALLCWMETHOD("MyGraphVar", "addLine", 10, 20, 40, 20)
REG[0]= CALLCWMETHOD("MyGraphVar", "addLine", 40, 20, 40, 40)
REG[0]= CALLCWMETHOD("MyGraphVar", "addLine", 40, 40, 60, 40)
REG[0]= CALLCWMETHOD("MyGraphVar", "addLine", 80, 0, 80, 100)
REG[0]= CALLCWMETHOD("MyGraphVar", "addLine", 90, 0, 90, 100)
REG[0]= CALLCWMETHOD("MyGraphVar", "addRect", 25, 100, 50, 75)
REG[0]= CALLCWMETHOD("MyGraphVar", "setPenColor", "#ff0000");red
REG[0]= CALLCWMETHOD("MyGraphVar", "setFillColor", "#ffff00");yellow
REG[0]= CALLCWMETHOD("MyGraphVar", "addCircle", -12.5, 62.5, 12.5)
REG[0]= CALLCWMETHOD("MyGraphVar", "setFillColor");off/default
REG[0]= CALLCWMETHOD("MyGraphVar", "setPenColor");off/default
//M(MyGraphSampleMask/"SlEsGraphCustomWidget Sample")
REG[0]= CALLCWMETHOD("MyGraphVar", "addArc", 100, 37.5, 125, 62.5, 0, 180)
REG[0]= CALLCWMETHOD("MyGraphVar", "update")
END_PRESS
Note
The display is not real-time capable.
Description
The properties listed in the following section can be read with ReadCWProperty() and written
with WriteCWProperty().
Examples
Reading the "CursorX" property of the SlEsGraphCustomWidget linked using display variable
"MyGraphVar". The result is written to register 0.
REG[0] = ReadCWProperty("MyGraphVar", "CursorX")
7.5.4 Properties
Overview
Property Description
AxisNameX Axis identifiers, X axis
AxisNameY Axis identifiers, Y axis
AxisNameY2 Axis identifiers, second Y axis (right)
AxisY2Visible Display/hide second Y axis (right)
AxisY2Offset Offset second Y axis (right)
AxisY2Factor Factor second Y axis (right)
ScaleTextEmbedded Position of the scaling texts
ScaleTextOrientationYAxis Alignment of the scaling texts of the Y axis
KeepAspectRatio Keep aspect ratios
SelectedContour Name of the currently selected contour
BackColor Background color
ChartBackColor Background color of the drawing area
ForeColor Foreground color for text and default pen color
ForeColorY2 Foreground color for the texts of the second Y axis (right)
GridColor Color of the grid lines
GridColorY2 Color of the horizontal grid lines of the second Y axis (right)
CursorColor Color of the cursor crosshairs
ShowCursor Display/hide cursor
CursorX Cursor X position
CursorY Cursor Y position
CursorY2 Cursor Y position referred to the second Y axis (right)
CursorStyle Cursor display type
ViewMoveZoomMode Response when zooming and shifting using gestures
Together with the "AxisY2Offset" property, it is possible to display a second Y axis (right) with
its own scaling. The scale is coupled coupled to the first Y axis (left) through an offset and a
factor.
Formula for converting Y2 to Y:
Y = Y2 / factor - offset
Formula for converting Y to Y2:
Y2 = (Y + offset) * factor
Example
Y: 0 to 200 should correspond to Y2: -25 to 25.
● Offset: -100
● Factor: 0.25
Calculation example:
Y2 = -30
Y = -30 / 0.25 – (-100) = -20
Calculation example:
Y=0
Y2 = (0 + (-100)) * 0.25 = -25
Example
Scaling text outside the drawing area:
ScaleTextEmbedded = FALSE
Example
Scaling text within the drawing area:
● ScaleTextEmbedded = TRUE
Horizontal text alignment:
● ScaleTextOrientationYAxis = 1
Figure 7-5 Scaling text within the drawing area, horizontal text alignment
Figure 7-6 Scaling text within the drawing area, vertical text alignment
Figure 7-7 Scaling text outside the drawing area, horizontal text alignment
Figure 7-8 Scaling text outside the drawing area, vertical text alignment
Example
setView(-15, -15, 15, 15)
setFillColor("#A0A0A4")
addCircle(0, 0, 5)
KeepAspectRatio = TRUE
KeepAspectRatio = TRUE
Note
In order to be able to execute operations on a contour, e.g. to add a graphic object, you must
first select this.
GridColorY2 - color of the horizontal grid lines of the second Y axis (right)
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
7.5.5 Functions
You can call the subsequently listed functions using the CallCWMethod() function.
Example
Setting the view of the SlEsGraphCustomWidget link using display variable "MyGraphVar".
The result is written to register 0.
REG[0] = CallCWMethod("MyGraphVar", "setView", -8, -5, 11- 20)
Overview
Function Description
setView Sets coordinate system
setMaxContourObjects Sets maximum number of objects for a contour (ring buffer)
addContour Adds a contour
showContour Shows a contour
hideContour Hides a contour
hideAllContours Hides all contours
removeContour Removes a contour
clearContour Deletes graphic object of a contour
fitViewToContours Automatic adaptation of the view
fitViewToContour Automatic adaptation of the view
findX Searches in a contour
setPolylineMode Displays points of a contour as polyline/curve
setIntegralFillMode Displays points of a contour as polyline/curve
repaint, update Refreshes view
addPoint Adds a point to a contour
addLine Adds a line to a contour
addRect Adds a rectangle to a contour
addRoundedRect Adds a rectangle with rounded corners to a contour
addEllipse Adds an ellipse to a contour
addCircle Adds a circle to a contour
addArc Adds an arc to a contour
addText Adds text to a contour
setPenWidth Sets the pen width
setPenStyle Sets the pen style
setPenColor Sets the pen color
setFillColor Sets fill color
setCursorPosition Positions the cursor
setCursorPositionY2 Positions the cursor referred to the second Y axis (right)
setCursorOnContour Positions the cursor on contour
moveCursorOnContourBegin Positions the cursor to the first graphic object of a contour
moveCursorOnContourEnd Positions the cursor to the last graphic object of a contour
Function Description
moveCursorOnContourNext Positions the cursor to the next graphic object of a contour
serialize Saves/restores the actual state
Note
This function automatically refreshes the display.
Example
Note
This function automatically refreshes the display.
Note
The display is automatically updated if you set the cursor using this function.
Example
setIntegralFillMode – fills the areas between points, lines and arcs and the X axis
Example
● update()
The function refreshes the view, assuming that the Widget refresh is not deactivated, and
the Widget is not hidden. The function is optimized so that the application performance is
maintained, and the view does not flicker as a result of excessively high refresh rates.
● repaint()
The function refreshes the view directly after the function call. Therefore, you should only
use the repaint function if an immediate refresh is absolutely necessary, e.g. for animation
purposes
It is recommended that you always work with the update() function. Internally, the
SlEsGraphCustomWidget always works with the function update() e.g. for setView().
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Example
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
Note
This function automatically refreshes the display.
7.5.6 Signals
You can capture the subsequently described ViewChanged signal in the configuration and
respond appropriately.
Overview
Function Description
ViewChanged Changing the view
Syntax: SUB(on_<GraphVarName>_ViewChanged)
…
END_SUB
Description: The "ViewChanged“ signal is sent if the view changes. You can respond to this
in the configuration in a specific SUB method. The SIGARG parameters are
appropriately set.
Parameters: GraphVarName Name of the display variable which contains a SlEs‐
GraphCustomWidget
SIGARG[0] left-hand edge (double)
SIGARG[1] upper edge (double)
SIGARG[2] right-hand edge (double)
SIGARG[3] lower edge (double)
Example
DEF MyGraphVar = (W///,"slesgraphcustomwidget.SlEsGraphCustomWidget"/////
10,10,340,340/0,0,0,0)
SUB(on_MyGraphVar_ViewChanged
DLGL("Current view: " << SIGARG[0] << ", " << SIGARG[1] << ", " << SIGARG[2]
<< ", " << SIGARG[3]
END_SUB
Result
After activation is complete, the softkey for the "Custom" operating area can be found in the
main menu (F10) on the menu continuation bar on the HSK4 (= default).
The "Custom" operating area displays an empty window covering the entire operating area,
with a configurable header. All horizontal and vertical softkeys can be configured.
The following options are available for configuring the start softkey:
1. To replace a softkey label with a language-dependent text, the following must be entered
in the [Custom] section:
TextId=MY_TEXT_ID
TextFile=mytextfile
TextContext=mycontext
In this example, the softkey shows the language-dependent text which was saved with the
text ID "MY_TEXT_ID" in text file mytextfile_xxx.qm under "MyContext" (xxx stands for
language code).
2. To replace a softkey label with a language-neutral text, the following must be entered in
the [Custom] section:
TextId=HELLO
TextFile=<empty>
TextContext=<empty>
In this example, the softkey for the "Custom" operating area displays the text "HELLO" for
every language.
3. An icon can also be displayed on the softkey in addition to the text.
To do this, the following must be entered in the [Custom] section:
Picture=mypicture.png
The softkey then displays the icon from the file mypicture.png. Graphics and bitmaps are
stored at the following path: [System oem directory]/ico/ico<Resolution>. The directory that
corresponds to the display resolution must be used.
4. The position of the softkey can also be set. The following entry in the [Custom] section
makes this setting:
SoftkeyPosition=12
The default is position 12. This corresponds to the HSK4 on the menu continuation bar of
the operating area's menu. Positions 1 - 8 correspond to HSK1 to HSK8 on the menu bar,
positions 9 - 16 to HSK1 to HSK8 on the menu continuation bar.
3. You create the custom.com project file in the [System oem directory]/proj directory. This
contains the relevant configuration which is created in the same way as the aeditor.com
file of the "Program" operating area. The configured start softkeys are then displayed in the
"Custom" operating area.
4. You configure the language-neutral text for the title bar of the dialog in the custom.ini file.
The following entry is available in the template for this purpose:
[Header]
Text=Custom
You can replace this text with a customized one.
5. The template contains the following entry for configuring a start screen for the "Custom"
operating area:
[Picture]
Picture=logo.png
Logo.png is the name of the start screen which appears on the "Custom" operating area's
start dialog. Here you can display a company logo, for example, or another image. The file
should be saved in the directory for the corresponding resolution under: [System oem
directory]/ico/ …
6. In order to display a specific "Run MyScreens" screen when the "Custom" operating area
is shown the first time, the following entry is available in the template:
; Mask shown with startup of area "custom"
[Startup]
;Startup = Mask:=MyCustomStartupMask, File:=mycustommasks.com
Typically, SINUMERIK Operate is started directly with a specific "Run MyScreens" screen.
The "startuparea" key must be set as follows in the "[miscellaneous]" section of the
systemconfiguration.ini file:
[miscellaneous]
;name of the area to be shown at system startup
startuparea = Custom
Example
File overview
The following files are required:
● custom.com
● easyscreen.ini
Programming
Content of the custom.com file:
Note
The graphic file mcp.png integrated in the example is also only a sample file. If you wish to
use this programming example in your application, you must replace the graphic by one of
your own graphics.
//S(Start)
HS7=("Start example", se1, ac7)
PRESS(HS7)
LM("Maske4")
END_PRESS
//END
//M(Maske4/"Example: MCP"/"mcp.png")
DEF byte=(I/0/0/"Input byte=0 (default)","Byte number:",""/wr1,li1///380,40,100/480,40,50)
DEF Feed=(IBB//0/"","Feed override",""/wr1//"EB3"/20,180,100/130,180,100), Axistop=(B//0/"","Feed
stop",""/wr1//"E2.2"/280,180,100/380,180,50/100)
DEF Spin=(IBB//0/"","Spindle override",""/wr1//"EB0"/20,210,100/130,210,100), spinstop=(B//
0/"","Spindle stop",""/wr1//"E2.4"/280,210,100/380,210,50/100)
DEF custom1=(IBB//0/""," User keys 1",""/wr1//"EB7.7"/20,240,100/130,240,100)
DEF custom2=(IBB//0/"","User keys 2",""/wr1//"EB7.5"/20,270,100/130,270,100)
DEF By1
DEF By2
DEF By3
DEF By6
DEF By7
PRESS(VS7)
EXIT
END_PRESS
PRESS(VS8)
EXIT
END_PRESS
LOAD
By1=1
By2=2
By3=3
By6=6
By7=7
END_LOAD
PRESS(HS1)
Byte.wr=2
END_PRESS
CHANGE(Byte)
By1=byte+1
By2=byte+2
By3=byte+3
By6=byte+6
By7=byte+7
Feed.VAR="EB"<<By3
Spin.VAR="EB"<<Byte
Custom1.VAR="EB"<<By6
Custom2.VAR="EB"<<By7
Axisstop.VAR="E"<<By2<<".2"
Spinstop.VAR="E"<<By2<<".4"
Byte.wr=1
END_CHANGE
CHANGE(Axis stop)
IF Axistop==0
Axistop.BC=9
ELSE
Axistop.BC=11
ENDIF
END_CHANGE
CHANGE(Spin stop)
IF Spinstop==0
Spinstop.BC=9
ELSE
Spinstop.BC=11
ENDIF
END_CHANGE
//END
Configuration
Description of the procedure:
● The systemconfiguration.ini contains a section [keyconfiguration]. The entry specifies an
action for a special PLC softkey.
● A number is given as an action. A "Run MyScreens" call is involved if the number is greater
than or equal to 100.
● A section for defining the action to be performed must be created in the easyscreen.ini file.
The name of the section is based on the name of the operating area and the dialog name
(see entry under [keyconfiguration] → Area:=..., Dialog:=...) → [<Area>_<Dialog>]
→ e.g. [AreaParameter_SlPaDialog].
● The action numbers (which were given in the systemconfiguration.ini → see Action:=...) are
defined in this section. There are two commands involved:
1. LS("Softkey menu1","param.com") ... Loading a softkey menu
2. LM("Screen form1","param.com") ... Loading a screen form
[keyconfiguration]
KEY75.1 = Area:=area, Dialog:=dialog, Screen:=screen, Action:= 100,
The LM and LS commands to be executed upon activation of the relevant PLC softkeys are
configured in the easyscreen.ini file. The names of the sections that are used for the purpose
of configuration are structured as follows:
[areaname_dialogname] The first part of the name "areaname" refers to the operating
area and the second part "dialogname" designates the dialog
to which the commands configured in this section apply.
The names given in the systemconfiguration.ini file for the op‐
erating area and dialog should be used. The dialog does not
have to be specified.
This is particularly true for operating areas which are only im‐
[AreaParameter_SlPaDialog] plemented by means of a single dialog. Please refer to the ex‐
100.screen1 = LS("Softkey1","param.com") ample on the left.
101.screen3 = LM("Screen
form1","param.com") If "screen1" is displayed in the AreaParameter operating area
implemented by the SlPaDialog dialog, the "LS("Softkey1","par‐
am.com")" command will be executed when the "action" with
the value 100 occurs.
action.screen=Command Both the "action" and "screen" attributes clearly indicate when
the specified command will be executed.
The "screen" information is optional.
The following commands are permissible:
LM (LoadMask)
LS (LoadSoftkeys)
Field of application
The following functions can be initiated in the operating software by the PLC:
● Select an operating area
● Select certain scenarios within operating areas
● Execute functions configured at softkeys
Hardkeys
All keys - also the PLC keys - are subsequently referred to as hardkeys. A maximum of 254
hardkeys can be defined. The following allocation applies:
Configuration
The configuring is realized in the systemconfiguration.ini configuration file in the section
[keyconfiguration]. Each line defines what is known as a hardkey event. A hardkey event is
the n-th actuation of a specific hardkey. For example, the second and third actuation of a
specific hardkey can result in different responses.
The entries in the systemconfiguration.ini configuration file can be overwritten with user-
specific settings. The directories [System user directory]/cfg and [System oem directory]/cfg
are available for this purpose.
The lines for configuring the hardkey events have the following structure:
Requirement
The PLC user program must fulfill the following requirement:
Only one hardkey is processed. As a consequence, a new request can only be set if the
operating software has acknowledged the previous request. If the PLC user program derives
the hardkey from an MCP key, it must provide sufficient buffer storage of the key(s) to ensure
that no fast keystrokes are lost.
PLC interface
An area to select a hardkey is provided in the PLC interface. The area is in DB19.DBB10.
Here, the PLC can directly specify a key value of between 50 and 254.
Acknowledgment by the operating software takes place in two steps. This procedure is
necessary so that the operating software can correctly identify two separate events if the same
key code is entered twice consecutively. In the first step, control information 255 is written to
byte DB19.DBB10. This defined virtual key stroke enables the HMI to identify every PLC key
sequence uniquely. The control information is of no significance to the PLC user program and
must not be changed. In the second step, the actual acknowledgment takes place with respect
to the PLC by clearing DB19.DBB10. From this point in time, the PLC user program can specify
a new hardkey. In parallel, the actual hardkey request is processed in the operating software.
Example
Configuration file:
; PLC hardkeys (KEY50-KEY254)
[keyconfiguration]
KEY50.0 = name := AreaMachine, dialog := SlMachine
KEY51.0 = name := AreaParameter, dialog := SlParameter
KEY52.0 = name := AreaProgramEdit, dialog := SlProgramEdit
KEY53.0 = name := AreaProgramManager, dialog := SlPmDialog
KEY54.0 = name := AreaDiagnosis, dialog := SlDgDialog
KEY55.0 = name := AreaStartup, dialog := SlSuDialog
KEY56.0 = name := Custom, dialog := SlEsCustomDialog
The area and dialog identifiers can be found in the systemconfiguration.ini from [System
Siemens directory]/cfg.
Turning
The following tables list the possible start softkeys for turning technology. Assignments of
individual start softkeys can differ depending on the particular system. The specified OEM
softkeys are permitted for "Run MyScreens".
programGUIDE (G-Code) start softkeys:
VSK7 Positions OEM Plunge turn‐ OEM OEM Spigot res. -- OEM
ing residual mat.
material
VSK8 Repeat posi‐ -- >> << Contour << >> <<
tion. milling
See also
Defining the start softkey (Page 28)
Milling
The following tables list the possible start softkeys for milling technology. Assignments of
individual start softkeys can differ depending on the particular system. The specified OEM
softkeys are permitted for "Run MyScreens".
programGUIDE (G-Code) start softkeys:
System colors
A uniform color table is available for configuring dialogs (subset of the respective standard
colors). The color of an element (text, input field, background, etc.) can be selected from the
following options (between 0 and 133).
As an alternative to the predefined colors, you can also specify colors as RGB values
("#RRGGBB").
2 Orange
3 Dark green
4 Light gray
5 Dark gray
6 Blue
7 Red
9 Yellow
10 White
Supported languages
Standard languages:
Other languages:
References
List Manual System Variables/PGAsl/
CB0
The CHANGE method is triggered when the screen is displayed if the variable has a valid
value at this time (e.g. through default setting or NC/PLC variable).
CB1 (default)
The CHANGE method is not explicitly triggered when the screen is displayed. If the variable
has a configured NC/PLC variable, then the CHANGE method is of course still called.
Condition Response
Type System or user variable Default setting Execute the CHANGE
method
I/O field Yes Yes Yes Due to the configured NC/PLC var‐
No iable, there is always at least one
automatic call of the CHANGE
No Yes method with the current value of
No the NC/PLC variable. The pre-as‐
signment of CB does not have an
effect.
No Yes Yes The CHANGE method is called
with the pre-assigned value.
No The CHANGE method is not called.
No Yes No call because there is no valid
No value present to call the CHANGE
method.
Toggle Yes Yes Yes Due to the configured NC/PLC var‐
No iable, there is always at least one
automatic call of the CHANGE
No Yes method with the current value of
No the NC/PLC variable. The pre-as‐
signment of CB does not have an
effect.
No Yes Yes The CHANGE method is called
with the pre-assigned value.
No The CHANGE method is not called.
No Yes The CHANGE method is called
(per default the with the first pre-assigned value of
first value from the the toggle list.
toggle is assigned) No The CHANGE method is not called.
See also
CHANGE (Page 100)
DEF MyVar=(R3///,"X1",,"mm"/WR1//"$AA_IM[0]")
CHANGE(MyVar)
IF MyVar.VAL < 100
HLP="mypic1.png"
ELSE
HLP="mypic2.png"
ENDIF
END_CHANGE
Recommendation:
CHANGE(MyVar)
IF MyVar.VAL < 100
IF HLP <> "mypic1.png"
HLP="mypic1.png"
ENDIF
ELSE
IF HLP <> "smypic2.png"
HLP="mypic2.png"
ENDIF
ENDIF
END_CHANGE
Example:
A name resolution is performed via RNP() for each change of the axis motion in order to
read channel-specific machine data:
CHANGE(AXIS_POSITION_X)
DLGL("Axis """ << RNP("$MC_AXCONF_GEOAX_NAME_TAB[0]") << """
has moved: "
<< AXIS_POSITION_X)
END_CHANGE
Keep the channel-specific machine data up-to-date with the aid of an invisible variable, copy
each value change to a temporary variable, e.g. register.
This temporary variable can then be used in the CHANGE method of the value change for
the axis position without making a name resolution of the machine data each time and the
subsequent read access:
CHANGE(AXIS_NAME_X)
REG[0] = AXIS_NAME_X
END_CHANGE
CHANGE(AXIS_POSITION_X1)
DLGL("Axis """ << REG[0] << """ has moved " << AXIS_POSITION_X)
END_CHANGE
● The update rate and therefore the execution of the associated CHANGE method of
variables that are connected to system or user variables with very frequent value changes,
can be reduced by using the UR variable property, e.g. variable that is coupled to the actual
axis values.
Reason:
In this way, the associated CHANGE method is executed in a fixed specified grid for a value
change.
Note that the number of script lines executed "in one operation", is currently limited to 10,000.
When this number is reached, the script execution is aborted with an appropriate entry in the
easyscreen_log.txt file.
Reason:
● Prevention of endless loops
● "Run MyScreens" must remain operable
Introduction
The manual describes working with the X3D Viewer with which you can integrate animated
and non-animated graphical scenes (animated elements) – called help screens in the following
– into the graphical user interface of SINUMERIK Operate as of Version V4.7 SP1 .
You can show motion sequences and parameters in context-sensitive help screens. This helps
you to improve the operation of applications and make the user interface more appealing.
Implementation of your initial idea to the final help screen is described in the steps below:
● Creation of graphical elements and 3D models for the help screens that will eventually
appear in the X3D Viewer (see Chapter Modeling (Page 248)).
● Creation of the scene description file in which the model data of the graphics file will be
assigned to the scenes and animations to be displayed at particular points (see Chapter
Structure of the scene description file (Page 255)).
● Conversion of the X3D files and XML files into HMI files (see Chapter Conversion to hmi
file (Page 259)).
● C++ integration of the X3D Viewer into your own application (see Chapter Implementation
example (Page 261)).
● Application in Run MyScreens (see Chapter Display in Run MyScreens (Page 262)).
C.2 Modeling
C.2.1 Requirements
The aim of the modeling is to create a file with the generated 3D models in .x3d file format, an
official standard for 3D contents.
Modeling is performed in the Flux Studio Web3D authoring tool . The Flux Studio Web3D
authoring tool is a freely available 3D modeling tool with versatile export and import options.
Requirements
● You have installed the Flux Studio Web3D authoring tool, Version 2.1.
● You are familiar with modeling and use of Flux Studio.
● File format .x3d is not described in any detail in this document, adequate knowledge of the
subject is assumed.
Note
You can download the Flux Studio Web3D authoring tool from the Internet via the following
link:
http://mediamachines.wordpress.com/flux-player-and-flux-studio (http://
mediamachines.wordpress.com/flux-player-and-flux-studio)
7. We recommend the following settings for texts (see also the following dialog box):
– Texts must always be centered.
– The size of the text should be 0.2. This size allows you to position the text easily. The
text output by the X3D Viewer is in the font size of the user interface, irrespective of this
value.
8. To create hatching, use file schnitt.png as the texture. The lines always go from the bottom
left to the top right at an angle of 45°. You should set the scaling to 3 in both dimensions.
The rotation depends on the construction type and must be adapted manually.
See also
XML commands (Page 254)
Import as inline
Flux Studio uses the object "Inline" for importing .x3d files. It allows you to link in external
elements without multiplying the 3D data of these models.
Insert the object with menu item Create -> Create Inline. Then enter a file name in the object
properties.
The model data from the Cinema4D file is inserted as a complete group. All cameras and any
other information that is additionally imported should be deleted. Only the graphics elements
of the Cinema4D file are required.
General
Template Description
intersection_texture.png Texture for an sectioned area
rapid_traverse_line_hori.fxw Horizontal line to illustrate the tool traversing path
during rapid traverse
rapid_traverse_line_vert.fxw Vertical line to illustrate the tool traversing path
during rapid traverse
Template Description
feed_traverse_line_hori.fxw Horizontal line to illustrate the tool path during feed
feed_traverse_line_vert.fxw Vertical line to illustrate the tool path during feed
dimensioning_lines_hori.fxw Horizontal projection lines
dimensioning_lines_vert.fxw Vertical projection lines
z1_inc.fxw Horizontal dimension line with the identifier Z1
x1_inc.fxw Vertical dimension line with the identifier X1
3d_coordinate_origin.fxw 3D coordinate origin
3d_zero_point.fxw 3D zero point
Turning
Template Description
turning_blank.fxw The blank for turning technology: A simple cylinder
turning_centerline.fxw Center line
turning_centerpoint.fxw Coordinate origin to display the zero point in the
WCS
turning_refpoint.fxw Reference point, for example, for a machining op‐
eration
turning_machining_area.fxw Boundary lines for the machining area
Milling
Template Description
milling_blank.fxw The blank for milling technology: A simple cube
milling_centerline.fxw Center line
milling_refpoint.fxw Reference point, for example, for a machining op‐
eration
C.3.1 Overview
The scene description file (extension .xml) is required so that the X3D Viewer can access the
graphics. In the scene description file, you assign the scene names that are called from the
configuration to the times in the .x3d file (time sensor) at which the graphics are positioned.
Description
Description
<TextPosition center='true' /> Marking that the texts are centered. This is rel‐
evant to the display of the texts in rotated
screens. We recommend using this setting.
Description
<!--Definition of an animation-->
<SceneKey name='BoringAnimation' masterRotationSpeed="-64.0"
maxRotAngle="45.0" begin-Time='0.110 endTime='0.118 view='camiso'
speedMaster='boringtool' Type="VIEW_3D_TURN_CYL">
Description
Description
Description
Description
Description
Description
Examples
mirror="RotatePieceZ=180"
mirror="RotatePieceZ=-90 MirrorScreenX"
mirror="RotateScreenY=90"
mirror="MirrorPieceX MirrorPieceY"
mirror="MirrorPieceZ RotatePieceX=-90"
Description
Note
The X3D files and their associated XML files are converted to HMI files when the HMI is
powered up.
For each X3D file, a corresponding XML file of the same name must be created. To do this,
you store the X3D files and XML files in directory search path of HMI\ico\x3d
\turning or milling. You proceed in the same way with the .ts files.
Parameters Meaning
pParent The parameter is passed on to the constructor of
the Qwidget.
~SlX3dViewerWidget ( )
Destructor of the X3D Viewer widget.
Parameters Meaning
- -
void viewSceneSlot ( const QString& rsFileName, const QString& rsScene, const QString&
rsAnimationScene, int nChannel, int nPlane, SlStepTechnology nTechnology )
With the viewSceneSlot method, the X3D Viewer is instructed to load the rsScene static scene
and the rsAnimationSzene animated scene from the rsFileName file and display them
alternately.
The static scene and then the animated scene are repeatedly alternately displayed for a fixed
time.
If no static scene is specified, the animation will be shown immediately; an animated scene
may also not have been specified.
Channel number, plane and technology are used to rotate the scenes to the correct position
(depending on the set machine coordinate system).
Parameters Meaning
rsFileName Name of the file that contains the scenes to be
displayed
rsScene Name of the static scene.
rsAnimationScene Name of the animated scene.
nChannel Channel number
Parameters Meaning
nPlane Plane
nTechnology Technology
The following constants are defined for the SlStep‐
Technology enumeration type:
● SL_STEP_NO_TECHNOLOGY
● SL_STEP_MILLING
● SL_STEP_TURNING
● SL_STEP_SURFACE_GRINDING
● SL_STEP_CIRCULAR_GRINDING
void viewSceneSlot ( const QString& rsFileName, const QString& rsScene, const QString&
rsAnimationScene )
A simplified form of the viewSceneSlot method with which the X3D Viewer can be instructed
to load and display the rsScene static scene and/or the rsAnimationSzene animated scene
from the rsFileName file.
Parameters Meaning
rsFileName Name of the file that contains the scenes to be
displayed.
rsScene Name of the static scene.
rsAnimationScene Name of the animated scene.
C.5.5 Libraries
In order to be able to apply the X3D Viewer in your own projects, the list of library dependencies
must be extended by the 'slx3dviewer.lib' entry.
//M(MASK_F_DR_O1_MAIN/$85407////52,80/XG1)
The following parameters are required to activate the individual help screens; their meaning
is described in Section 5.3 Public slots:
1. File name
2. StaticScene (optional)
3. AnimationScene (optional)
4. Technology (optional)
5. Plane (optional)
The parameters are combined into a character string in this order, separated by a comma.
Examples
● The default help screen can be set with the specified variable Hlp.
In the following example, the "MyAnimation" animation is output from the "MyDlgHelp.hmi"
file. No StaticScene is specified, i.e. no static scene is output. No specifications are made
for the Technology and Plane, i. e. default values are used.
Hlp = "MyDlgHelp.hmi,,MyAnimation"
● The hlp property can be set on a specific help screen for the individual parameters of the
input screen.
In the following example, the static "MyParam" scene and the "MyAnimation" animation are
output from the "MyDlgHelp.hmi" file in the G17 plane. No specification is made for the
Technology, i.e. a default value is used.
VarMyParam.hlp = "MyDlgHelp.hmi,MyParam,MyAnimation,,G17"
Access level
Graduated system of authorization, which makes the accessibility and utilization of functions
on the operator interface dependent on the authorization rights of the user.
Array
An array can be used to organize data of a standard data type stored in the memory in such
a way that it is possible to access the data via an index.
Attribute
Characteristic that assigns specific → Properties to an object (→ Dialog or → Variable).
Column index
Column number of an array
Configuration file
File, which contains definitions and instructions that determine the appearance of → Dialogs
and their → Functions.
Definition lines
Program section in which → Variables and softkeys are defined
Dialog
Display of the → User interface
● Dialog-dependent softkey menu
Softkey menu, which is called from a newly configured dialog.
● Dialog-independent softkeys
Softkeys, which are not called from a dialog, i.e., start softkey and softkey menus, which
the user configures before the first, new dialog.
Editor
ASCII Editor with which characters can be entered in a file and edited.
Event
Any action, which initiates execution of a → Method: Input of characters, actuation of softkeys,
etc.
Group
Reload unit for → Configuration file
Help variable
Internal arithmetic variable to which no → Properties can be assigned and is not, therefore,
visible in the → Dialog.
Hotkeys
6 keys on OP 010, OP 010C and SINUMERIK keyboards with hotkey blocks. Pressing the
keys selects an operating area directly. As an option, 2 additional keys can be configured as
hotkeys.
Input/output field
Also I/O field: for inputting or outputting variable values.
Interpreter
The interpreter automatically converts the defined code from the → Configuration file into a
→ Dialog and controls its use.
Line index
Row number of an array
Menu tree
A group of interlinked → Dialogs
Method
Programmed sequence of operations executed when a corresponding → Event occurs.
Parameter
Parameters are variable elements of the programming syntax and are replaced by other words/
symbols in the → Configuration file.
PI service
Function which, on an NC, executes a clearly defined operation. PI services can be called from
the PLC and the HMI system.
Programming support
Provision of → Dialogs to assist programmers in writing → Parts programs with "higher-level"
components
Properties
Characteristics of an object (e.g of a → Variable)
Recompile
NC code sections can be generated in a → Part program from input fields in → Dialogs in the
→ Programming support system. Recompilation is the reverse operation. The input fields used
to generate a selected section of NC code are retrieved from the NC code and displayed in
the original dialog.
Selecting
A program formulated in the NC language, which specifies motion sequences for axes and
various special actions.
Simulation
Simulation of a → Parts program run without movement of the actual machine axes.
Softkey labels
Text/image on the screen, which is assigned to a softkey.
Softkey menu
All horizontal or all vertical softkeys
Start softkey
Softkey with which the first newly created → Dialog is started.
Toggle field
A list of values in the → Input/output field; check with toggle field: The value input in a field must
be the same as one of the listed values.
User variable
Variables defined by the user in the → Parts program or data block.
Variable
Designation of a memory location, which can be displayed in a → Dialog by assigning
→ Properties and in which input data and the results of arithmetic operations can be entered.
B F
Background color, 75 File
Copy, 118
Delete, 118
C Moving, 120
File formats
Colors, 75
fxw, 247
Comparison operators, 97
hmi, 247
Conditions, 98
x3d, 247
Configuration file, 25
xml, 247
Configuration syntax"; "Extended syntax, 36
Flux Studio Web3D authoring tool, 248
Configuration syntax"; "Screens, 36
Focus control, 178
Configuration syntax"; "Softkey, 37
Foreground color, 75
Configuration syntax"; "Table columns, 37
Function
Configuration syntax"; "Variables, 36
CALL (Subprogram call), 114
Configuring PLC softkeys, 229
CLEAR_BACKGROUND), 117
Constants, 97
CP (Copy Program), 118
Custom widget
CVAR (Check Variable), 116
Automatic data exchange, 182
Cyclic execution of scripts, 164
Definition, 179
DEBUG, 125
Executing a method, 185
DLGL (Dialog line), 124
Interface, 180
DO LOOP), 162
Library, 179
DP (Delete Program), 118
Manual data exchange, 183
EP (Exist Program), 119
Reading and writing properties, 183
EVAL (Evaluate), 130
Responding to a custom widget signal, 187
EXIT, 126
EXITLS (EXIT Loading Softkey), 131
FCT, 131
D File access, 122
Default setting, 72 FORMAT (string), 160
Defines the softkey menu, 53 GC (Generate Code), 133
HMI_LOGIN, 136
HMI_LOGOFF, 136
HMI_SETPASSWD, 136 G
INSTR (String), 156
Generates NC code, 133
LA (Load Array), 137
Graphic text, 72
LB (Load Block), 138
Grid → Table, 174
LEFT (string), 157
LEN (string), 156
LISTADDITEM), 128
LISTCLEAR), 128
H
LISTCOUNT), 128 H_SEPARATOR (define horizontal dividing
LISTDELETEITEM, 128 line), 169
LISTINSERTITEM, 128 Help display, 75
LM (Load Mask), 139 Help file, 76
LS (Load Softkey), 140 Help variable, 64
MIDS (string), 158
MP (Move Program), 120
MRDOP), 113 I
MRNP (Multiple Read NC PLC), 143
I/O field with integrated unit selection, 76
Overview, 112
Image as short text, 68
PI_START, 145
Import
RDFILE), 122
Graphics (models), 251
RDLINEFILE), 122
Input mode, 74
RDOP), 113
Reading and writing drive parameters, 113
Recompile NC code, 150
Recompile without comment, 152
L
REPLACE (string), 158 Language code, 239
RESIZE_VAR_IO, 147 Limits, 72
RESIZE_VAR_TXT, 147 LINE (define line), 167
RETURN (Back), 149 List field, 68
RIGHT (string), 157 Long text, 72
RNP (Read NC PLC Variable), 146
SB (Search Backward), 154
SF (Search Forward), 154 M
SP (Select Program), 121
Machine data, 261
START_TIMER), 164
Machining step support, 152
STOP_TIMER, 164
Master dialog, 139
STRCMP (string), 158
Mathematical functions, 96
STRINSERT (string), 159
Menu tree, 27
STRREMOVE (string), 159
Method
SWITCH), 143
ACCESSLEVEL, 100
TRIMLEFT (string), 160
CHANGE, 100
TRIMRIGHT (string), 160
CHANNEL, 102
UNTIL, 162
CONTROL, 102
WDOP, 113
LANGUAGE, 104
WHILE, 162
LOAD, 104
WNP (Write NC PLC Variable), 146
LOAD GRID, 141
WRFILE, 122
OUTPUT, 106
WRLINEFILE), 122
Overview, 100
PRESS, 107
PRESS(ENTER), 108
T
Table
Defining columns, 177
Definition, 174
Programming, 176
Text, 72
Toggle field, 67, 72, 80
Toggle symbol, 73
Tooltip, 72, 74
Trigonometric functions, 96
U
Unit text, 72
Update rate, 73
User variable, 75
V
V_SEPARATOR (define vertical dividing line), 168
Variable
calculating, 64
Change property, 76
Commissioning Manual
Valid for:
10/2015
6FC5397-1DP40-5BA3
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 System settings............................................................................................................................................5
1.1 Delivery condition of the system..............................................................................................5
1.2 Meaning of switch positions.....................................................................................................7
1.3 System booting........................................................................................................................8
1.4 Displays during system booting...............................................................................................9
2 Configuring the system...............................................................................................................................13
2.1 Ethernet interfaces of the NCU..............................................................................................13
2.2 How to determine the IP address of the NCU........................................................................14
2.3 Configuration file "basesys.ini"...............................................................................................15
2.3.1 Section [ExternalInterface].....................................................................................................15
2.3.2 Section [InternalInterface]......................................................................................................18
2.3.3 Section [IBNInterface]............................................................................................................21
2.3.4 Section [SNMP]......................................................................................................................22
2.3.5 Section [DCP].........................................................................................................................24
2.3.6 Section [LLDP]......................................................................................................................24
2.3.7 Section [LinuxBase]...............................................................................................................25
2.3.8 Example: Configuration file 'basesys.ini'................................................................................28
2.4 Service Commands................................................................................................................35
2.4.1 Using service commands.......................................................................................................35
2.4.2 Syntax for the Actions............................................................................................................36
2.4.3 Generic elements...................................................................................................................37
2.5 Description of the actions.......................................................................................................39
2.5.1 Help........................................................................................................................................39
2.5.2 Check-cf.................................................................................................................................40
2.5.3 Clear.......................................................................................................................................40
2.5.4 Closeport................................................................................................................................40
2.5.5 Connect..................................................................................................................................41
2.5.6 Disable...................................................................................................................................43
2.5.7 Disconnect.............................................................................................................................44
2.5.8 Distribute................................................................................................................................44
2.5.9 Enable....................................................................................................................................45
2.5.10 Openport................................................................................................................................47
2.5.11 Port status..............................................................................................................................48
2.5.12 Restart....................................................................................................................................48
2.5.13 Restore...................................................................................................................................49
2.5.14 Save.......................................................................................................................................50
2.5.15 Show......................................................................................................................................51
2.5.16 Start, Stop..............................................................................................................................55
3 Service and diagnostics..............................................................................................................................57
3.1 Creating a service system......................................................................................................57
Scope of validity
This document is valid for all systems that are supplied with Linux as operating system on the
CompactFlash Card, such as all NCUs of the type NCU 7x0.3
Directory Use
/siemens Reserved for Siemens system software
/addon Reserved for Siemens add-on software
/oem Additional software and configurations of the machine manufacturer
/user ● Storage of user data
● Configuring the HMI application
● Data that is created when commissioning the system using the HMI
application.
/system Linux operating system
/user/system/etc File basesys.ini (modifications possible)
/user/common/tcu TCU configuration files
/var/log/messages System log file (same as event.log under Windows)
Note
Files in the directory under /user always have priority over files with the same name in the
directory /oem → /addon → /siemens.
Preset users
The following users have already been set up:
Overview
The NCU has two twist buttons in the lower section of the front panel.
3/&
Sequence
To ensure unproblematic booting of the NCU, the CompactFlash Card must be inserted.
When the NCU is booting up, visual information on the current operating system is provided
using the following displays:
● The RDY-LED flashes slowly orange when the CF card is accessed.
● During booting, the 7-segment display outputs different codes that indicate, for example,
when the BIOS is started, when the CompactFlash Card is accessed, etc.
When the booting has been completed successfully, the following is displayed:
● The PLC LED lights up green.
● The 7-segment display shows "6." with a flashing dot.
● The RDY-LED lights up green. All other LEDs are not illuminated.
See also
How do you create a service system for the NCU? (Page 57)
SINAMICS faults and alarms, also see: SINAMICS S120/S150 List Manual (LH1)
Load BIOS
NRK/NCK outputs
System error
Supplementary conditions
For the operation of an NCU:
● No more than one NCU may be operated as a DHCP server on the system network.
● An external mouse is recommended when using the System Network Center.
Network interface
The network interface is an interface that enables network communication. These are the
Ethernet interfaces on the NCU.
Note
The IP addresses can also be set directly from the SINUMERIK Operate user interface in the
"Commissioning" → "Network" operating area.
Storage path
For a Linux basic system the original file can be found on the CompactFlash Card under the
path /system/usr/etc. OEM versions are stored under /oem/system/etc, as well as user
versions under /user/system/etc.
Use
Settings are made in the basesys.ini file that specify the behavior of the system in the network.
To edit the basesys.ini file:
● Comments are introduced by ';' or '#' at the beginning of the line, and span the width of the
line. Empty lines are also handled as comments.
● The sections that start with a "[NAME]" line are ignored by the basic system itself, but are
sometimes used by the HMI.
● Variable definitions are written in the form "NAME=VALUE". Blanks are permitted around
the '=' character. The value may also be enclosed in double quotation marks, but this is
optional.
Note
Suitable editors for Linux
In most Linux system files, lines may only be ended with LF, and not with CRLF as in
Windows. Please take note of this when selecting an editor. The HMI application editor
under "Commissioning” is suitable.
In the Linux operating system, the UNIX editor vi is available.
Please take note that the Linux operating system is case-sensitive.
Reference
To make settings in the basesys.ini file, dialogs are provided in the "Commissioning" operating
area in SINUMERIK Operate in order to display or modify the values of the individual variables:
Commissioning Manual "SINUMERIK Operate" (IM9)
Description
In this section, the parameters and settings for the external Ethernet interface are defined. For
an NCU7x0, this is X130 (Eth1). If the external interface is in DHCP mode, i.e. the value of
ExternalIP is empty or not defined, then all parameters listed here, with the exception of
"DHCPClientID", are accepted by the DHCP server as long as the server provides a value for
the parameter.
DisableCompanyNet
If this variable is set to 1, the X130 interface to the company network is not initialized and is
thus not available.
Value: Empty, 0 or 1
Default: Empty
ExternalIP
If ExternalIP is not empty, the fixed IP address specified there is used in the company network
interface. The ExternalNetMask then also needs to be set, as well as the gateway, name
servers, host name, and domain if required.
If ExternalIP is not set or is empty, a DHCP client is started on the interface.
Value: IP address
Default: Empty
ExternalNetMask
ExternalNetMask must be set together with ExternalIP, in order to define the size of the network.
Gateway
If the value of gateway is not empty, the host specified there is used as the default gateway,
which means that all IP packets that cannot be directly assigned are sent there for routing.
If no gateway is specified, only the networks that are directly connected are accessible.
Value: IP address
Default: Empty
Nameservers
If DNS name servers are specified here, then these must be used to resolve symbolic host
names, i.e. at most of the points where an IP address is expected, a computer name can also
be used instead.
The name server setting is also sent to your DHCP client (TCU, PG) via the DHCP server of
the NCU, so that this can also work with symbolic names.
Timeservers
Here you can specify a list of NTP servers (Network Time Protocol) that can be used by the
NTPD on the NCU for time synchronization. The status of NTPD is output in the system log
file /var/log/messages
Note
Setting the time zone and the time server
The IP addresses can also be set directly from the SINUMERIK Operate user interface in the
"Commissioning" → "Date time >" softkey operating area.
Hostname
Here you can define a name for the local host. This manually assigned name takes priority
over all other names.
The host name is determined in the following order:
● Host name from the basesys.ini file, if set.
● A name received from the DHCP server (if DHCP client mode and a name have been
supplied), the result of a reverse DNS lookup, i.e. which name belongs to the IP received
(if name servers are defined).
● Default name ("NONAME_...")
Because the host name is also used as DNS name it must satisfy the corresponding
requirements of the RFC:
● ASCII letters (a-z, A-Z), numbers (0-9) and '-'
● max. 63 characters
Value: Name
Default: Empty
Domain
These variables can be used to configure the DNS domain. The effect is that names in this
domain can be resolved without qualification (e.g. if the domain is "test.local", you can also
specify the name "computer1.test.local" as "computer1").
Value: Name
Default: Empty
DHCPClientID
With these variables, you can influence which ClientID the DHCP client presents to its server.
This ID can be used by the server to assign certain parameters to the client, for example a
static IP address.
Usually, the MAC address of the Ethernet interface is used for this purpose. This is also the
default setting. Alternatively, you can also use the host name ("@NAME"), which must then
be defined in the basesys.ini, in order to be recognized before the DHCP request. It is also
possible to use an arbitrary string for ClientID.
Description
In the section [InternalInterface] the data is specified for synchronization of the DHCP server
in the system network.
DisableSysNet
If this variable is set to 1, the X120 interface to the system network is not initialized and is thus
not available.
Value: Empty, 0 or 1
Default: Empty
InternalIP
Use this variable to set the fixed IP address in the system network. InternalIP should always
be used together with InternalNetMask.
Value: IP address
Default: 192.168.214.1
InternalNetMask
Specifies the subnet mask for InternallP and should always be used together with it.
InternalIP_Alias
Use this variable to define an additional alias IP address for the interface of the system network
(X120); this is practical in certain application cases.
Value: IP address
Default: Empty
InternalIP_Alias should always be used together with InternalNetMask_Alias.
InternalNetMask_Alias
This variable specifies the subnet mask for InternallP_Alias and should always be used
together with it.
EnableDHCPD_SysNet
If this variable is set to zero, then the start of the DHCP server in the system network X120 is
prevented.
Value: Empty, 0 or 1
Default: Empty
SyncModeDHCPD_SysNet
If this variable is not set to "OFF", the DHCP servers synchronize themselves in the system
network (X120) so that only one of them actively assigns addresses. This makes it possible
to operate multiple NCUs or PCUs concurrently without having to adjust the network settings.
The DHCP servers that are not active go into "standby" mode; in this mode they regularly get
the current address data and TCU data from the active server so that if the active server fails
a standby server can take over the active role without data loss.
● With the ON_MASTER setting instead of ON_HIGH you can influence the synchronization
in such a manner that the server with the "Master" setting is always the active server (for
this it must be active in the network). This means that in the normal situation
deterministically the same control is always the DHCP server and you can find the actual
address data (/var/etc/udhcp-eth0.leases) and the TCU data (/user/common/tcu/...) there.
ON_MASTER should only be set for a single DHCP server in the system network; there
should not be multiple masters.
● The ON_LOW setting assigns the DHCP server a lower priority than normal. It then
becomes the active server if no server with ON_HIGH or ON_MASTER is found in the
network.
Note
Compatibility with earlier versions
The priority level "ON_LOW" is used automatically if the DHCP server is switched off.
Although such an NCU does have a (standby) DHCP server and keeps a backup of the
lease data, normally, however, it does not become an active server.
InternalDynRangeStart
With the two variables InternalDynRangeStart and InternalDynRangeEnd, you can explicitly
specify the range of IP addresses assigned by the DHCP server. The number range of the
presetting should normally suffice.
Value: IP address
Default: First address in the system network + 10 or +2 (if ≤ 16 addresses)
InternalDynRangeEnd
Value: IP address
Default: Last address in the system network - 15 or -1 (if ≤ 16 addresses)
DHCPDNoMasterWait
If a synchronizing DHCP server has once "detected" a master server in the past, then it waits
for synchronization until the time specified here elapses before it becomes the active server.
This additional pause makes it possible for the intended DHCP master to become the active
DHCP server without displacement even if it is shortly switched on thereafter, or takes longer
to boot than other controls.
InternalDNSDomain
This is used to specify the Top Level Domain (TLD) name that is used in the system network.
The DNS server of the NCU assigns names to the devices in the system network in this zone.
Name requests for all other zones are forwarded to an external name server in the company
network.
As presetting the "local" recommended by the RFC1035 is used for local networks, to avoid
conflicts with globally defined domain names.
Recommendation: The default setting should be maintained.
DisableNATRouting
The default setting permits that a machine can access a company network from the system
network via the control using the NAT routing (= "Network Address Translation"). In this case,
the NCU converts the source address of the packets to its own address, and handles the
response packets in the inverse way.
If this variable is set to zero, the NAT routing of the NCU from the internal interfaces eth0
=X120 and ibn0 =X127 to the external network on eth1 =X130 is prevented. In order that the
NAT routing is not simultaneously shut down for both internal networks, using the values
"X120" or "X127", the system network or the commissioning network is selectively shut down.
Description
The settings in this section affect interface X127.
EnableDHCP_IBNNet
If this variable is set to 1 then this prevents the start of the DHCP server at the commissioning
interface X127.
Value: Empty, 0 or 1
Default: Empty
DisableIBNNet
If this variable is set to 0, then the commissioning interface X127 is not initialized and is thus
not available.
Value: Empty, 0 or 1
Default: Empty
EnableSysNetToIBNForwarding
If this variable is set to 1, it is possible to transfer packets from the system network (X120) to
X127. A firewall usually prevents this.
It is important to remember that there is no NAT involved, and the sender is responsible for
ensuring (with a suitable routing entry, for example) that packets sent to the PG or service PC
on X127 with the address 192.168.215.x only reach the NCU to which the device is connected.
Value: Empty, 0 or 1
Default: Empty
NOTICE
Security risk
Note that opening the firewall can represent a security risk. Permit feed-through only for the
period for which it is actually required. Note that every accessible service can have security
gaps.
DisableIBNForwarding
If this variable is set to 1, the NAT transfer of packets from the service connection X127 to the
system network (X120) is deactivated.
Value: Empty, 0 or 1
Default: Empty
Description
Character strings delivered via SNMP (Simple Network Management Protocol) are entered
here. This is a way of giving out information.
SNMPLocation
This string is used for the standard OID SNMPv2-MIB::sysLocation. It is possible to specify a
location here, which can be subsequently called with an SNMP client.
SNMPContact
This string is used for the standard OID SNMPv2-MIB::sysContact. It is possible to specify a
contact address here, which can be subsequently called with an SNMP client.
SNMPAutLocation
This string is used for the Siemens-specific OID
automationSystemIdent.automationLocationTag. It is possible to specify an additional location
here, which can be subsequently called with an SNMP client. This is similar to SNMPLocation
in terms of the MIB description, although it is intended for entries relating to automation.
SNMPFunction
This string is used for the Siemens-specific OID
automationSystemIdent.automationFunctionTag. It is possible to specify a function
designation here, which can be subsequently called with an SNMP client.
SNMPStation
This string is used for the SINUMERIK-specific OID
mcSinumerikMIB.mcSinumerikMiscStation. The value is the name of a station to which the
device belongs. Devices with the same station name are therefore identified as being
contiguous.
Description
The parameters in this section define the properties of the DCP protocol (Discovery and Basic
Configuration Protocol), e.g. that are used in the menu item "Accessible nodes" of STEP 7.
InternalDcpEnabled
This can be used to switch-on and switch-off the DCP in the system network (X120); for the
NCU, the value is also used for X127.
Value: 0 or 1
Default: 1
ExternalDcpEnabled
This can be used to switch-on and switch-off the DCP in the company network (X130).
Value: 0 or 1
Default: 0
Description
The parameters in this section define the properties of the LLDP protocol (Link Layer Discovery
Protocol), which is used by several applications for network diagnostics.
InternalLldpEnabled
This can be used to switch-on and switch-off the LLDP in the system network (X120); for the
NCU, the value is also used for X127.
Value: 0 or 1
Default: 1
ExternalLldpEnabled
This can be used to switch-on and switch-off the LLDP in the company network (X130).
Value: 0 or 1
Default: 0
InternalLldpTLVsTxEnabled
Using this parameter, additional information in the LLDP packets are enabled at X120/X127,
which are normally not included.
1: port description
2: system name
4: system description
8: capabilities
ExternalLldpTLVsTxEnabled
Using this parameter, additional information in the LLDP packets is enabled on the X130, which
are normally not included.
Description
Additional setting possibilities of the Linux system are combined in this section.
Timezone
The time zone set here is used by the system to convert UTC time (Universal Time
Coordinated) to local time. The time zone is sent to all applications via the environment variable
"TZ", and is taken into account by the libc function localtime().
The time zone influences all time entries in the basic system, particularly for the command
"date", for "ls -l", and in the system log file /var/log/messages.
Note
Setting the time zone and the time server
The IP addresses can also be set directly from the SINUMERIK Operate user interface in the
"Commissioning" → "Date time >" softkey operating area.
Syntax (obligatory):
tz offset Time zone and difference from UTC:
West of the zero meridian, the difference must be added; east of the zero
meridian, the difference must be subtracted.
Syntax (optional, only if there is daylight saving time):
dst,Mmwd,Mmwd Daylight saving time zone with beginning and end
m (1 ≤ m ≤ 12) m: Month
LogFileLimit
The size of the system log file /var/log/messages can be restricted with this variable. By
entering "Zero", the log file has no size limitations.
The specified limit is no hard limit for reasons of efficiency but rather a sort of target value. If
the log file reaches the target value times factor 1.5, then it is reduced to around 75% of the
target value. A check is carried out every two minutes maximum to see if the file has become
too large.
Value: Size in KB
Default: 100 KB
FirewallOpenPorts
Here you can specify a list of the ports which is to be enabled in the firewall of the external
network interface. The protocol is "TCP" or "UDP", the port is the (numerical) port number of
the service to be enabled. Several entries are separated by blanks.
NOTICE
Security risk
Note that opening the ports in the firewall can represent a security risk. Only enable the ports
that you actually require.
Note that every accessible service can have security gaps.
DisableSubsystems
Using this variable, you can suppress mounting and starting of certain subsystems (CFS
systems). Several subsystem names can also be specified - separated by blanks.
DisableNTPTimeSync
If this variable is set to 1, then the NTPD server (Network Time Protocol Daemon) for the time
synchronization is not started and the time of day is not synchronized.
Value: 0 or 1
Default: 0
DisablePLCTimeSync
If this variable is set to 1, synchronization of the system time with the PLC time (in both
directions) will not be executed.
Value: 0 or 1
Default: 0
EnableCoreDumps
If this variable is set to 1, a log file for processes is created and stored under /var/tmp. The
log file contains a memory dump of the process that has crashed or that has terminated.
Value: Empty, 0 or 1
Default: 0
CheckTCUforUpdatePackage
If this variable is set to 1, when booting, the USB interface at the front of the TCU is checked
to identify any storage medium. If, when checking the update packages, type *.usz files created
with Create MyConfig are found, then the installation of these update packages is started.
With the default setting zero, this check is skipped in order to save time.
Value: 0 or 1
Default: 0
;InternalIP_Alias=192.168.216.1
;InternalNetMask_Alias=255.255.255.0
; This defines a "name of station" for ProfiNet (ERTEC interface)
; for use with DCP, default is the normal hostname.
; Please be careful if a PN-Name can also be set by other means,
; for example by NCU-Link. Usually it is not needed to define
; a name here.
;PN_StationName="PN_IO"
; This is the range of dynamic IPs given out by the DHCP server
; Defaults should be sensible
InternalDynRangeStart=192.168.214.10InternalDynRangeEnd=192.168.214.
239
; If once a DHCP master was seen, the DHCP server waits this many
seconds
; for the master to show up before trying to become the active server
;DHCPDNoMasterWait=120
[IBNInterface]
; X120 to X127. (Please note that the sending host must be able to
route
; the packets to the NCU by its own means, the NCU just accepts and
forwards
; packets to 192.168.215.x with this setting.)
;EnableSysNetToIBNForwarding=1
[SNMP]
; The following variables define strings which are delivered on
; certain SNMP requests.
; SNMPLocation and SNMPContact are reported for the standard OIDs
; SNMPv2-MIB::sysLocation and SNMPv2-MIB::sysContact, resp.
; SNMPAutLocation and SNMPFunction are used in the Siemens A&D
specific
; AUTOMATION-SYSTEM-MIB as
automationSystemIdent.automationLocationTag
; and automationSystemIdent.automationFunctionTag, resp.
SNMPLocation="not specified"
SNMPContact="not specified"
SNMPAutLocation="not specified"
SNMPFunction="not specified"
SNMPStation=""
[DCP]
; These variables en/disable the DCP protocol on X120/X127
; and X130, resp.
;InternalDcpEnabled=0
;ExternalDcpEnabled=1
[LLDP]
; These variables en/disable the LLDP protocol on X120/X127
; and X130, resp.
;InternalLldpEnabled=0
;ExternalLldpEnabled=1
[LinuxBase]
; Properties of local time zone: names, offset, start and end day
; Some examples:
; Europe: WET0WEST,M3.5.0,M10.5.0
; CET-1CEST,M3.5.0,M10.5.0
; EET-2EEST,M3.5.0,M10.5.0
; USA: EST5EDT,M4.1.0,M10.5.0
; CST6CDT,M4.1.0,M10.5.0
; MST7MDT,M4.1.0,M10.5.0
; PST8PDT,M4.1.0,M10.5.0
; China: CST-8
; Japan: JST-9
Timezone=UTC
Overview
The service command 'sc' is a tool used for performing a range of service tasks on a
SINUMERIK NCU. The required action is written in the command line after the 'sc', e.g.: sc
help
This action produces a list of all actions with a short description. After the action, further
parameters or options can follow.
'sc' is available in both the NCU basic system and the service system (mostly in the form of a
USB memory.) However, some actions are only useful in one of the two systems (NCU/
Service). This is noted for each action.
See also
The most important terms and abbreviations are explained in the glossary.
Privilege levels
The 'sc' command can execute its actions using more privileges than are normally granted to
the calling user. For example, starting or stopping subsystems requires root privileges, but 'sc'
allows every user who belongs to the ‘service’ group to do this.
Each action of 'sc' is assigned a “privilege level”. This is a user group to which the user must
belong in order to execute the action. As the groups are hierarchically nested, members of
“higher” groups can also use the action in question. For example, the group 'manufact' is above
'service', which means that members of the group 'manufact' can call all actions that require
the privilege level 'service'.
The privilege level that the caller requires is noted for each individual action. The possible
levels are (in ascending order):
● none
● operator
● user
● service
● manufact
Example:
An action with the privilege level 'user' can also always be executed by members of the groups
'service' and 'manufact'. Actions with privilege level ‘none’ can be called by all users.
If a user does not have the required privileges, the following error message is output:
Action 'ACTION' needs at least GROUP privilege level.
Description
'sc' in the command line is essentially not case-sensitive.
The following entries are therefore interpreted as identical:
sc help show
SC help SHOW
sc HeLp sHoW
In some cases, however, upper/lower case can make a difference, for example in file or user
names. This is avoided wherever possible.
The conventions used are as follows:
● Names completely in upper case represent objects to be used depending on the situation.
Example: sc help ACTION
In this case, ACTION is to be replaced by the action for which you want a description. If
written in lower case, however, the entry should be entered as specified.
● Square brackets indicate optional entries.
Example: sc help [ACTION]
In this case the specification of an action is optional, which means that you can enter an
action, but do not have to. Square brackets may also be nested:
... [USERNAME[/DOMAIN]] ...
In this case, USERNAME and DOMAIN are both optional, but you can only enter a DOMAIN
if you have also entered the USERNAME.
● Alternatives are separated with '|'.
Example: sc start all|system|SUBSYSTEM
This means that any of the following commands applies:
sc start all
sc start system
sc start SUBSYSTEM
In the latter case, SUBSYSTEM in upper case can be replaced by a concrete subsystem
name.
● As a shortened form, alternatives can also be written in square brackets:
sc save [-full|-user] ...
Here you can use the option "-full" or "-user", or none at all.
● Options that begin with '-' can always be entered in any order.
For example, the notation could be interpreted to mean that "-force" must come after "-full"
or "-user", but this is not necessarily the case:
sc save [-full|-user] [-force] FILENAME
Overview
This sections describes the syntax elements that are used by several actions.
Subsystem
A subsystem is a CFS that not only contains a collection of files, but also executes a program,
for example, at runtime. To do this, the CFS contains a script that is used to control the starting
and stopping of this program.
For this reason, only administrators are permitted to set up NFS file systems, and NFS is
usually only implemented in uniformly administrated environments. Exported file systems on
the server are addressed directly on the server via their path.
2.5.1 Help
Description
2.5.2 Check-cf
Description
Syntax: sc check-df
Alternative names: checkcf
Authorization level: user
With this action, the CompactFlash Card is read to check whether it contains defective sectors.
If errors occur, this is noted in the /var/log/messages file.
2.5.3 Clear
Description
Various actions can be performed with the "sc clear" command; only the "clear dhcp" command
is relevant here.
clear dhcp
Note
The clearing of the Lease data does not delete the entire file, but only the data contained
therein. This action also increments the version number, so that available standby DHCP
servers can also perform the deletion.
2.5.4 Closeport
Description
Syntax: sc closeport ID
Alternative names: ---
Authorization level: service
Principle of operation
This command closes a port in the firewall opened previously with the "sc openport" command.
This is only necessary when the port is to be closed manually before the time set with "sc
openport" expires. Otherwise the port is closed automatically when the port service life expires.
One parameter is the ID number of the firewall rule output by "sc openport".
2.5.5 Connect
Description
NOTICE
Password protection
Note that when entering this command, the password appears on the screen in plain text
according to the specified syntax.
For path names, use the slash “/” and not the backslash “\”.
SMB: //[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE
The fixed share is: //SERVER/SHARE
The server name can of course also be a numeric IP address. SHARE is the name of the
release on the server. Note that the character '$', which often occurs in this type of name, must
be preceded by a backslash ('\') in the command line. Otherwise, the system tries to expand
a variable.
A user name can also be entered in front of the server name, separated with a '@' character.
If necessary, the user name can also be extended by adding '/' followed by the Windows domain
to which it belongs. The password belonging to this user is normally queried interactively, so
that it is not visible on the screen.
For some applications, however, it may be necessary to write the password in the command
line. (For example, programs started from WinSCP cannot read from the keyboard.) In this
case, you can append an additional '%' character, followed by the password. If this contains
any special characters that are interpreted by the shell (<, >, &, ;, ", ', $, (, ), |), you should
shield these by preceding them with a backslash. Commas in SMB passwords cannot be
interpreted.
NFS: SERVER:/PATH
In NFS, entering the user is not required, which just leaves the two components SERVER and
PATH. As before, SERVER is the name of the file server. In contrast to SMB, PATH is a path
name that exists on the server, and not an arbitrarily assigned name.
The command "sc show drives SERVER" shows the file systems offered by a particular server
in the correct notation. For SMB, if required, the user name, etc. still need to be added.
After the entry of the remote file system, you can also specify the required directory
('MOUNTPOINT') in which the remote files will become visible locally. This should be an empty
directory to which you have write access. If MOUNTPOINT is omitted, 'sc' itself generates a
suitable directory. The name is /tmp/drvNN (numbered consecutively), and is displayed when
the connection is successful.
The "-ro" option connects the remote file system in read-only mode, this means that you can
only read and do not have write access. This can be useful if you want to exclude changes
that originate from the control, or if the server only allows read-only connections.
As explained above, an SMB file system is connected as the specified user. To prevent a third
user from executing file operations on the control in the name of the connected user, the local
directory can normally only be accessed by the latter (and all members of the same group).
However, if you do want to make the remote directory available to further local users, you can
use the "-public" option to make the MOUNTPOINT belong to the "operator" group, and this
access is therefore guaranteed.
2.5.6 Disable
Description
Note
The "sc disable" command acts on the parameters in the basesys.ini file located in the card/
user/system/etc/basesys.ini directory.
"sc disable IPAlias" deactivates the second alias IP address for the X120 network interface.
See also
"InternalIP_Alias" and "InternalNetMask_Alias" parameters in the "basesys.ini" file.
Special subsystems
The "DHCPSvr" name is a special case. This does not switch a normal subsystem on or off,
but specifies whether or not a DHCP server should be started on a network interface. The
interface is entered in the standard form.
The synchronization of the DHCP server is switched on and off with "DHCPSync". The
synchronization is only possible in the system network.
The "sc enable" and "sc disable" commands function by changing certain variables in the /user/
system/etc/basesys.ini file. The associated variable is "DisableSubsystems" or
"DisableDHCPD<INTERFACE>" for subsystems and DHCPSvr, respectively.
"sc disable usb" locks USB storage devices: Specifically, the devices of USB class "storage"
are involved, i.e. input devices can still be operated at the USB interface.
● Without a time specification [-MINUTES] , a permanent disable is set. When a time is
specified, the inhibit is specified in minutes.
● The inhibit can refer to all network participants of the system network or a list with host
names or IP addresses can be specified, for which the inhibit is valid.
2.5.7 Disconnect
Description
2.5.8 Distribute
Description
distribute tcudata
Note
This command can be performed on any machine in the system network, not only on the active
server. A message is always sent to the active server.
2.5.9 Enable
Description
Note
The "sc enable" command acts on the parameters in the basesys.ini file located in the card/
user/system/etc/basesys.ini directory.
"sc enable IPAlias" defines a second alias IP address for a network interface. This is only
supported for X120. The IP address itself has the usual notation with four numbers separated
by decimal points. If not specified, the subnet mask can be determined from the class (A/B/C)
of the IP or determined explicitly. The CIDR notation (number of bits of the network section)
is also possible.
See also
"InternalIP_Alias" and "InternalNetMask_Alias" parameters in the "basesys.ini" file.
Special subsystems
The "DHCPSvr" name is a special case. This does not switch a normal subsystem on or off,
but specifies whether or not a DHCP server should be started on a network interface. The
interface is entered in the standard form.
The "sc enable" and "sc disable" commands function by changing certain variables in the /user/
system/etc/basesys.ini file. The associated variable is "DisableSubsystems" or
"DisableDHCPD<INTERFACE>" for subsystems and DHCPSvr, respectively.
With "sc enable usb" USB storage devices on permanently disabled USB interfaces or on
certain host names or IP addresses are enabled again.
DHCP synchronization
The synchronization of the DHCP server is switched on and off with "DHCPSync". The
synchronization is only possible in the system network (X120). A priority can also be specified:
-LOW, -HIGH or -MASTER.
The priorities have the following effect for the synchronization of the DHCP server:
● MASTER: The computer node becomes an active DHCP server. If several servers have
been configured in the system network, this computer has the highest priority.
● HIGH: The computer node belongs to the server candidates with high priority, i.e. if no
server with "MASTER" priority becomes active, then a computer with "HIGH" priority can
be the active server.
● LOW: The computer node belongs to the server candidates with low priority, i.e. if no server
with "MASTER" priority or "HIGH" priority becomes active, then a computer with "LOW"
priority can be the active server.
Note
Recommended settings are:
● DHCP operation and DHCP synchronization are switched on in the system network.
● Exactly one NCU is set as DHCP server.
● A maximum of two computers are candidates with "HIGH" priority.
● All other components are set as DHCP clients or candidates with "LOW" priority.
See also
"SyncModeDHCPD_SysNet" parameter in the "basesys.ini" file.
2.5.10 Openport
Description
Principle of operation
This command opens a port in the firewall to the company network (X130) for a certain time.
The default time is 15 minutes, but this can be changed with the -MINUTES option. The
maximum possible time is 60 minutes.
The port to be opened is specified in the form "PROTO/PORTNR". The protocol can be either
"tcp" or "udp". This is followed by the specification of the hosts from which the port should be
accessible. Several forms are possible here:
● A single IP address: "128.128.12.12"
● A host name (if this can be resolved via DNS), e.g. "server"
● An IP area with net mask specification, e.g. "128.128.12.0/255.255.255.0"
● An IP area with specification of the valid bits, e.g. "128.128.12.0/24"
If the specification of the source host is completely missing, this is normally acknowledged with
an error message. However, an exception is when the "sc openport" command is entered in
a shell opened via SSH. The permitted host is taken from the $SSH_CLIENT environment
variable that contains the IP of the SSH client.
If the opening was successful, an ID number is output in a status message:
sc: Port tcp/25 is open, rule ID is 6620
This ID can be used with "sc closeport" to manually close the port earlier.
NOTICE
Security risk
Note that opening the ports in the firewall can represent a security risk. Only enable the ports
that you actually require.
Note that every accessible service can have security gaps.
See also
"FirewallOpenPorts" parameter in the "basesys.ini" file.
Description
Principle of operation
The "sc portstatus" command queries whether a specific port in the firewall is open. The "-
x127" option must be specified if X127 rather than the X130 firewall is concerned. The port
specification is identical to "sc openport", e.g. "tcp/102". However, no names are permitted
here and the specified source IP must be unique.
The following status is output:
● "Port not open" with exit status 1.
● "Port is open (rule ID is <N>)." and exit status 0.
Whereby, the ID required for "sc closeport" must also be specified.
2.5.12 Restart
Description
Syntax
'hmi', 'nck' or any other subsystem names can be used as subsystems. Multiple subsystems
can also be specified successively; they (including all required dependencies) are then started
and stopped in this order. It is also possible to start and stop all subsystems, other than the
named ones. To do this, prefix an exclamation mark "!" to the list.
"all", "system" and "network" are special values for the subsystem:
● "all" stops and starts all available subsystems.
● In contrast, "sc restart system" initiates a cold restart of the system (reboot).
● "network" may be specified only together with "restart". "sc restart network" reinitializes the
network, e.g. after settings have been changed in basesys.ini.
Examples
# Stop all subsystems:
$ sc stop all
# Stop only HMI:
$ sc stop hmi
# Start HMI and NCK:
$ sc start hmi nck
# Start all subsystems other than NCK:
$ sc start ! nck
2.5.13 Restore
Description
Principle of operation
As for "sc save", a restore is possible only from the service system or when the subsystems
are stopped. If "sc restore" reports an error, for example that the restore will cause running
subsystems to crash, you can use the "sc save" option to force the operation, as for "-force".
Normally, "sc restore" deletes the complete target area before the backup is restored (complete
CompactFlash Card for full backup, /user in user data backups). This means that no files are
subsequently available that were not included in the backup.
Options
If no further options are specified, the archive should represent a full backup and this should
be restored in full. The status of all files is therefore the same after the "restore" as it was at
the time of the backup.
● The -full option additionally forces the partition and the file system to be recreated on the
CompactFlash Card. This is, however, possible only from a service system. -full is
necessary if the partition table and/or file system is missing or damaged.
● However, if you want to restore the backup files without losing any files that have been
created in the meantime, you can use the "-nodelete" option to prevent them from being
deleted. "-nodelete" is not executed together with "-full", because all data is always deleted
when the file system is recreated.
● The -addon, -oem, -user, -addon+ and -oem+ options also allow only parts of an archive
to be unpacked.
● The -update option is used to load software updates supplied by Siemens. The -update
option can also be useful with -restart. If user-defined system files are changed when
loading the archive to the control, a cold restart or reinitialization is necessary. In such
cases, "sc restore" outputs an appropriate message at the end of the operation. The -restart
option causes the required action to be performed automatically.
2.5.14 Save
Description
Options
The following options are used for selecting which directories of the file system are to be written
to the archive:
-full: complete backup (default): all files of the control, incl. Boot Loader
-addon: only /addon directory
-oem: only /oem directory
-user: only /user directory (user data)
-addon+: /addon, /oem and /user
-oem+: /oem and /user
If "sc save" is used directly on the control, and the subsystems are running, this could lead to
inconsistencies between saved files because they could still change during the backup
process. Therefore, in this case "sc save" normally ends in an error message to inform that
subsystems are still running.
● If you want to create a backup anyway, you can use the -force option. Although "sc save"
still issues a warning, the process continues. If "sc save" is started from the service system,
assuredly no subsystems of the control are running and "-force" is not necessary.
● The -update option writes an Img-D control file to the archive. This makes it possible to use
the archive later via "sc restore -update".
Example:
sc save -user /tmp/drv01/backup.tgz
2.5.15 Show
Description
show ip
configured: (default)
current : IP=192.168.214.1 Netmask=255.255.255.0
MAC=08:00:06:73:55:fd
DNS Name : ncu1.local
Nameserver: 127.0.0.1
DNS Suffix: local
DHCP : synced server, prio=high, active
Statistics: RX=0.0MB (0.00% errors), TX=0.2MB (0.00% errors)
X130 (company network, eth1):
configured: DHCP
current : IP=111.222.333.64 Netmask=255.255.248.0
MAC=08:00:06:73:55:fe
DNS Name : name.test.siemens.de
Nameserver: 111.222.333.12 111.222.333.13 111.222.333.14
DNS Suffix: test.siemens.de
DHCP : client (server: 111.222.333.221)
Statistics: RX=1.2MB (0.00% errors), TX=0.0MB (0.00% errors)
X127 (engineering network, ibn0):
current : IP=192.168.215.1 Netmask=255.255.255.224
MAC=08:00:06:73:55:ff
DNS Name : ncu-ibn
DHCP : server
Statistics: RX=0.0MB (0.00% errors), TX=0.0MB (0.00% errors)
Default gateway: 111.222.333.1 (via eth1)
Used nameserver: 127.0.0.1
Used DNS suffix: test.siemens.de local
When all interfaces are displayed, the default gateway is also output, i.e. the address of a
router to which all packets are sent that cannot reach their destination directly via a local
interface.
The default gateway is therefore a piece of data that applies to all interfaces and of which there
is only one instance. However, there is one interface via which it must be possible to address
the default gateway. This is displayed in brackets after the address.
show drives
Examples
Notation:
sc show drives someuser/somedomain@somepc # Windows-Server
Password: *******
//somepc/C$
//somepc/D$
//somepc/images
sc show drives someserver # NFS-Server
someserver:/export/home1
someserver:/export/home2
sc show drives TCU # TCU USB-Medien
TCU1:/dev0-0
TCU2:/dev0-0
All the available remote file systems of the relevant server are listed in the notation that is also
expected by "sc connect".
● In NFS file systems, the server name is always first, followed by a colon and then the export
path.
● A USB storage medium on a TCU is a special form of NFS, and therefore also has the
same notation as an NFS file system. The specified path exists - but not physically - on the
TCU, but is converted there to USB by the NFS server.
show net
Options
The various switches, which can also be combined, allow additional information to be output
on the devices found:
● Unless additional options are involved, the output format for "sc show net" is designed to
be displayed on the screen. The alternative XML format is preferable, however, if further
machine-based processing is required. This can be selected via the -xml option (this option
must be the first one!).
● If the command line contains nothing after the switches, "sc show net" will search the
complete system network via broadcast for devices able to use SNMP. This search takes
time, however, and in the case of larger systems, the volume of information output can be
considerable. In view of this, a list of IP addresses or (DNS) names can be specified to
ensure a better overview. This will limit the search process and only the named devices will
be included.
-hw Information on hardware, such as the MLFB, serial number, hardware ID,
hardware version, SRM version, manufacturer, and the serial number of the
CompactFlash Card. Some devices have two of these hardware blocks (the
second one being intended for an integrated device).
The PLC in the NCU and the TACO in the OP on an TCU are two such ex‐
amples.
-tco Operating state data: Switching counter, operating hours counter, quantity of
data written to the CompactFlash Card, number of times maximum tempera‐
ture exceeded.
-loc Location data: Location, function, and contact details for the device (if config‐
ured there).
-sw Displays brief details of the software installed, only the version of the overall
status (or of the basic system if only this is installed).
-swfull Displays all the installed software components. They are represented hier‐
archically in the form of a tree. The following is provided for each component:
Information about the version, internal version (if different), target version (if
different), version details, and the installation path.
-panel: Displays panel-specific data: Size and color depth of the display, MCP/TCU/
DCK/EKS index, and the VNC server currently represented
Note
The data and information read out here are automatically written to the EUNA file (End User
Notification Administration), and saved on the associated device.
Description
Note
Only "all" and "system" function, but not arbitrary subsystems. Both of these actions have been
implemented only to a limited extent.
Subsystem names
"hmi", "nck" or any other names can be used for the subsystems. Multiple subsystems can
also be specified successively; they are then started and stopped in this order.
"all" and "system" are special values for the subsystem:
● "all" starts or stops all available subsystems.
● "sc stop system" also stops all subsystems and the basic system with the control.
● "sc start system" is identical to "sc start all" and exists mainly for reasons of symmetry.
Overview
To backup user data or the complete CompactFlash Card, proceed as follows:
● Creating a service system.
● Backing up the license
● Backup: Data backup on USB storage medium or on a network drive.
● System diagnostics
– Output network settings
– Changing the network settings
– Starting the VNC Viewer
To restore the user data or the complete CompactFlash Card, proceed as follows:
● Restore/Recover: Restore the data from USB storage medium or from network drive.
● Carry out software update.
● Carry out firmware update.
Purpose
In case service is needed, create a portable "Emergency Boot System" (EBS) on a USB
memory. Thus you can start the booting of the NCU from the service system in order to carry
out various service tasks, such as data backup or updates, in a service shell.
Two partitions are created on the service system:
● A Linux partition that is not displayed under Windows.
● An FAT partition, to backup files or save software updates.
The FAT partition can be read and written to under Linux as well as from a Windows system.
The FAT partition can be addressed under the path/data in a command shell under Linux.
Scope of delivery
To create a service system on a USB storage medium, the following files are included on CD:
● an executable file installdisk.exe
● an image file for USB-FlashDrive
● a file with the latest information siemensd.txt / siemense.txt
Recommendation:
It is better to use SIMATIC PC USB-FlashDrive.
Note
To create the service system, you need administrator rights.
All data already on the USB storage medium will be deleted.
The transfer is optimized for USB 2.0; therefore, the transmission to the USB storage medium
takes longer when using USB 1.1 than USB 2.0
Proceed as follows
To create a service system on a USB storage medium:
1. Copy the service system onto a local hard disk of your PG/PC.
2. Connect the USB storage medium to the USB interface of the PG/PC.
3. Determine in Windows Explorer which drive letter the USB storage medium was assigned,
e.g. H:
4. Open a DOS shell and change to the directory in which the files for the service system are
stored.
5. In the DOS shell, enter the following command:
installdisk ––verbose ––blocksize 1m linuxbase.img h:
Result: The image is transferred to the USB storage medium.
Note
Operation with touch panels
The service system does not support any touch operation.
● SINUMERIK OP 019: An external keyboard is required for text input (connection via USB).
● SIMATIC Thin Client: You activate the integrated keyboard here.
● FPGA
● CBE30 Bootloader
VNC Viewer Start a VNC Viewer Calling the VNC Viewer (Page 87)
Diagnosis Starting a diagnostic function to display net‐ Performing system diagnostics
work-connection data and data on the sys‐ (Page 82)
tem CompactFlash Card.
Backup NCU Software and Data Backup system and user data on the USB Backup data via the service menu
FlashDrive or network drive. (Page 66)
Update NCU Software and Data Upgrade the system from the USB Flash‐ This is how you update the software
Drive or network drive. (Page 80)
3. Register yourself with a user name with access authorization to this drive.
Note the syntax of the examples specified:
Application
For the following cases, backup the license key of the CompactFlash Card on a USB storage
medium or on a network drive:
● Software update without license key
● System software error without defective hardware
Note
Replacement CompactFlash Card
The following data are required in order to obtain a valid license key after replacing the system
CompactFlash Card: The serial number of the defective and the new CompactFlash Card.
2. Select the menu item "Backup license key to USB memory stick".
The following menu is displayed:
The license key is backed up in the specified directory together with the serial number of the
CompactFlash Card.
See also
The procedure is essentially the same as for "Backup license key to network drive". In addition,
you connect to a network drive:
This is how you connect to a network drive (Page 61)
4. Confirm with "Ok". The following message is output after the operation has been
successfully completed:
Note
Backup file ≥ 4GB
For a backup file ≥ 4GB, the space on the FAT partition of the service system (with 8GB)
is no longer sufficient. For this reason, backup files of this size are partitioned (see also: sc
save/sc restore) or they can be saved on a network drive.
See also
The procedure for "Backup user data to network drive" is analog. In addition, you connect to
a network drive:
This is how you connect to a network drive (Page 61)
2. Select "Restore user data from USB memory stick" and confirm with "Ok".
The list of the tgz files available on the USB storage medium are displayed.
3. Select the appropriate tgz file and confirm with "Ok".
A message is output after the operation has been successfully completed.
See also
The procedure for "Restore user data from network drive" is essentially the same. In addition,
you connect to a network drive:
This is how you connect to a network drive (Page 61)
3.3.3 This is how you create a complete backup of the CompactFlash Card
2. Select "Backup complete CF card to USB memory stick" and confirm with "OK".
See also
The procedure for "Backup complete CF card to network drive" is essentially the same. In
addition, you connect to a network drive:
This is how you connect to a network drive (Page 61)
NOTICE
Formatting
This procedure corresponds to formatting the CompactFlash Card and all of the existing data
are overwritten.
2. Select the menu item "Recover system from USB memory stick (reformat CF card)" and
confirm with "Ok".
The list of the tgz files available on the USB storage medium are displayed.
3. Select the appropriate tgz file and confirm with "Ok".
A message is output after the operation has been successfully completed.
Completion
The system must be restarted in order that the new data become effective.
See also
The procedure for "Recover system from network drive (reformat CF card)" is essentially the
same. In addition, you connect to a network drive:
This is how you connect to a network drive (Page 61)
(I) Configuration of NCU with TCU: the service shell is called under Linux.
(II) Configuring the NCU with PCU 50 or programming device (PG).
A service shell can be called under:
● on the NCU under Linux
● on the PCU/PG using the VNC Viewer (system network or company network)
● on the PCU/PG using WinSCP (system network or company network)
Proceed as follows
To back up the complete system:
1. Connect the service system to a USB interface (X125 or X135) of the NCU and press the
reset button.
Alternatively, you can switch the NCU off, connect the service system, and switch the NCU
on again.
Result: The NCU boots from the service system.
2. In the main menu, select the menu item "Service Shell".
3. Log on as a service technician using the user name "manufact" and password "SUNRISE".
4. Using the command "sc backup" you can create the backup file "backup01.tgz".
The directory /data on the service system is provided for backup files. The complete path
should be specified.
5. Choose –full, to backup all data on the CompactFlash Card, or –user, if you only want to
backup user data.
Example: sc backup –full /data/backup01.tgz
Result:
A backup file of the complete CompactFlash Card is created under /data on the service
system on the USB storage medium.
3.4.2 This is how you restore data from the service system
Proceed as follows
To restore the complete system:
1. Connect the service system to a USB interface (X125 or X135) of the NCU and press the
reset button.
Alternatively, you can switch the NCU off, connect the service system, and switch the NCU
on again.
Result: The NCU boots from the service system and the main menu is displayed.
2. In the main menu, select the menu item "Service Shell".
3. Log on as a service technician using the user name "manufact" and password "SUNRISE".
4. With the command "sc restore" you can write the backup file "backup01" from the service
system back to the CompactFlash Card in the NCU. The complete path should be specified.
Example: sc restore /data/backup01.tgz
Result:
The system state stored in the file "backup01" is restored on the NCU.
Note
If access to the system data on the CompactFlash Card is not possible because the
CompactFlash Card is defective or empty, you can only log in as user "admin" with the
password "SUNRISE" and no longer as the user "manufact".
Sequence
Proceed as follows:
● Connect the service system.
● "Service Shell" open.
● Establish a connection to a network drive.
● Create a backup file.
Scenario II: Start the command shell with WinSCP on the programming device:
Procedure:
1. Start WinSCP and enter the following data in the log-on window:
– IP address of the NCU (or, if required, host name)
– User name "manufact" with password "SUNRISE".
2. Select in the menu "Commands" → "Open Terminal".
3. Execute the data backup using the commands described in steps 4 to 6 from scenario I.
Scenario II: Start the command shell using the VNC Viewer on the programming device
Procedure:
1. Start the VNC Viewer and connect to the NCU using the IP address (or where relevant,
using the host name)
2. Log on under the "manufact" user name with the password "SUNRISE".
3. To restore the data, enter the corresponding commands as described under steps 3 to 5
in scenario I.
3.4.4 This is how you restore data from the network drive
Sequence
Proceed as follows:
● Connect the service system.
● "Service Shell" open.
● Establish a connection to a network drive.
● Restore the data.
Scenario II: Start the command shell with WinSCP on the programming device:
Procedure:
1. Start WinSCP and enter the following data in the log-on window:
– IP address of the NCU (or, if required, host name)
– User name "manufact" with password "SUNRISE".
2. Select in the menu "Commands" → "Open Terminal".
3. To restore the data, enter the corresponding commands as described under steps 3 to 5
in scenario I.
Scenario II: Start the command shell using the VNC Viewer on the programming device
Procedure:
1. Start the VNC Viewer and connect to the NCU using the IP address (or where relevant,
using the host name)
2. Log on under the "manufact" user name with the password "SUNRISE".
3. To restore the data, enter the corresponding commands as described under steps 3 to 5
in scenario I.
Firmware Update
When service is required, it may be necessary for a service technician to install a BIOS update.
Siemens provides the corresponding update file. Possible formats include: *.img or *.rom or
*.bin. Or, the update file is already supplied on the service system, then step 1 is eliminated.
Procedure:
1. Copy the update file to the FAT partition of the service system.
2. Connect the service system to interface X125 or X135 of the NCU.
3. Switch on the system.
4. In the main menu, select the menu item "Firmware Update".
The following menu is displayed:
Update / Recover
The following options are available:
● Update the software from the service system or from the network drive.
● Completely restore the CompactFlash Card with the system software from the service
system or from the network drive (Recover system ...).
2. Select the menu item "Update system software from USB memory stick".
The list of the tgz files available on the USB storage medium are displayed.
3. In order to check which software version contains the tgz file, first select the tgz file, then
press "Show version".
The following information is output:
Completion
The system must be restarted in order that the new data become effective.
See also
The procedure for "Update system software from network drive" is essentially the same. In
addition, you connect to a network drive: This is how you connect to a network drive
(Page 61)
For a complete backup of the system: This is how you install a complete system backup
(Page 72)
See also
This is how you check the CompactFlash Card (Page 85)
NOTICE
Reset ... data to factory defaults
The selected data are reset to the state when delivered, therefore overwriting all of the
previous specific commissioning settings that have been made.
Note
This procedure can take several minutes.
Application
The VNC Viewer is used to connect directly with a VNC Server and, for example, to operate
an HMI application.
Furthermore, it enables you to call up a list of all the network devices, thereby obtaining an
overview of the system network.
Number Meaning
Session 0 HMI-Applikation
Session 4 Command Shell
Session 5 System logfile
Session 6 System Network Center (SNC)
Use
The programs WinSCP and PuTTY are freely-available open source programs for Windows.
WinSCP is intended especially for transferring files from and to Linux systems, PuTTY for the
remote operation of a command shell.
● WinSCP can be downloaded via the following link: http://winscp.net/eng/download.php
(http://winscp.net/eng/download.php) (Installation Package).
WinSCP also offers a "command shell" that is limited so that commands can be issued, but
no callbacks can be answered.
● PuTTY, by contrast, offers a complete command shell.
PuTTY web page: http://www.chiark.greenend.org.uk/~sgtatham/putty (http://
www.chiark.greenend.org.uk/~sgtatham/putty)
With both programs, a service technician can log onto the NCU and carry out service tasks.
The username ‘manufact’ with the password ‘SUNRISE’ is available for the Siemens service
technician.
Starting WinSCP
WinSCP is started from Windows after the service technician has logged onto the NCU with
which he is connected using the corresponding authorization (e.g. as user "manufact" with
password "SUNRISE").
From the "Commands“ menu, select ”Open terminal” to open a command shell. There you can
carry out the service commands in the usual way.
TFTP Trivial File Transfer Protocol: Very simple data transmission protocol
UDP User Datagram Protocol: NTP is mostly processed via UDP.
USB Universal Serial Bus
UPS Uninterruptible power supply
UTC Universal Time, Coordinated: Coordinated Universal Time (previously: Greenwich Mean Time)
VNC Virtual Network Computing
C
B CFS (Compressed File System), 37
basesys.ini, 15 Coding switches, 7
CheckTCUforUpdatePackage, 28 Command
DHCPClientID, 18 Backup, 50
DHCPDNoMasterWait, 20 Check-cf, 40
DisableCompanyNet, 16 Closeport, 40
DisableIBNForwarding, 22 Connect, 41
DisableIBNNet, 22 Disable, 43
DisableNATRouting, 21 Disconnect, 44
DisableNTPTimeSync, 28 Enable, 45
DisablePLCTimeSync, 28 Help, 39
DisableSubsystems, 27 Openport, 47
DisableSysNet, 18 Port status, 48
Domain, 17 Reboot, 48
EnableCoreDumps, 28 Restart, 48
EnableDHCP_IBNNet, 21 Restore, 49
EnableDHCPD_SysNet, 19 Save, 50
EnableSysNetToIBNForwarding, 22 Show, 51
ExternalDcpEnabled, 24 Start, 55
ExternalIP, 16 Stop, 55
ExternalLldpEnabled, 24 CompactFlash Card
ExternalLldpTLVsTxEnabled, 25 Memory partitioning, 6
ExternalNetMask, 16 Partitions, 5
FirewallOpenPort, 27
Gateway, 16
Hostname, 17 D
InternalDcpEnabled, 24
data
InternalDNSDomain, 21
Restoring, 76
InternalDynRangeEnd, 20
DHCP synchronization, 46
InternalDynRangeStart, 20
InternalIP, 18
InternalIP_Alias, 19
InternalLldpEnabled, 24
E
InternalLldpTLVsTxEnabled, 25 Emergency Boot System, 57
InternalNetMask, 18 Ethernet interfaces, 13
InternalNetMask_Alias, 19
LogFileLimit, 27
Name servers, 16
Service system
Backing up data, 74
I Creating for the NCU, 58
Restoring data, 75
Interfaces
Service Tool WinSCP, 89
Ethernet, 37
SMB (Server Message Block), 38
NCU, 13
Subnet mask, 14
IP address
Subsystem, 37
Display, 14
Designation, 37
Synchronization
DHCP, 46
L System
Load operating system, 9 Diagnostics, 9
Log file, 5, 28
System error, 10
N
NCK commissioning switch, 7
NCU booting, 8
T
Network drive, 61 Time zone, 26
Network interface, 13
NFS (Network File System), 38
U
Update
P BIOS, 78
PLC mode switch, 7 Firmware, 78
Privilege, 35 User group, 35
Users (default setting), 6
R
Remote File System, 38
V
Replacement part, 63 VNC (Virtual Network Computing), 13
Reset
Button, 8
Execute, 8 W
WinSCP, 89
S
Section
[DCP], 24
[ExternalInterface], 15
[IBNInterface], 21
[InternalInterface], 18
[LinuxBase], 25
[LLDP], 24
[SNMP], 22
Service command
Application, 35
Rights, 35
Syntax, 36
Service menu, 60
___________________
Configuring the system 2
___________________
Install software and updates 3
SINUMERIK Backing up and restoring
___________________
data 4
SINUMERIK 840D sl
PCU-Basesoftware (IM8) ___________________
Service and diagnostics 5
___________________
List of Abbreviations A
Commissioning Manual
Valid for:
02/2014
6FC5397-1DP40-4BA0
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 3
Table of contents
PCU-Basesoftware (IM8)
4 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system 1
1.1 Delivery condition of the system
Overview
The PCU has onboard interfaces for communicating via Ethernet, MPI and PROFIBUS DP.
The integrated free slots remain free for other tasks. The PCU is equipped with the
Windows XP ProEmbSys operating system and for data backup tasks with the Symantec
Ghost software.
Interfaces:
● Four USB ports (USB 2.0) offer points where a keyboard, mouse and other peripheral
devices can be connected.
● For CF cards, there is a covered slot.
● Two internal PCI slots are available for specific expansions.
For commissioning:
● Two 7-segment displays and two LEDs are integrated for diagnostic purposes. They
indicate the current operating status and display the BIOS error codes during startup.
● If the PCU is to be operated without an operator panel front, a monitor and an additional
keyboard will also be required:
– For diagnostics during startup of the PCU.
– When installing a replacement hard disk
(alternatively, the hard disk can also be installed externally).
References: Operator Components and Networking Manual
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 5
Commissioning the system
1.1 Delivery condition of the system
Documentation for all Ghost tools is supplied on the PCU’s hard disk under E:\TOOLS
Note
For the system component versions contained in the PCU base software, see the
C:\BaseVers.txt file.
Note
Acknowledgements
• This product includes cryptographic software written by Eric Young ([email protected])
• This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit. (http://www.openssl.org/)
PCU-Basesoftware (IM8)
6 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.1 Delivery condition of the system
Memory segmentation
The hard disk of the PCU 50.3 has 40 GB of storage capacity and is segmented into a
primary partition C and an expanded partition with the three logical drives D, E and F which
operate with NTFS file access.
The PCU 50.5 is equipped with a solid state drive (SSD) with NTFS file access, which is also
segmented to provide a primary partition C and an expanded partition with the three logical
drives D, E and F. The SSD is available with 32 GB and 40 GB storage capacity.
Partitioning of the SSD with 40 GB is identical to that for partitioning of the hard disk.
Depending on the order, the operating software can already be installed when the unit is
shipped. It is installed subsequently by the customer the first time the system starts up. For
reasons of data security, the operating software and the Windows XP system software are
distributed over the different hard disk partitions.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 7
Commissioning the system
1.1 Delivery condition of the system
Note
Installing software
All of the applications must be exclusively installed on USER (F:) even if these applications
have a different drive set as the default drive in their installation path.
The partition names EMERGENCY, TMP, SYSTEM, USER must not be changed; otherwise
the "ServiceCenter" will no longer function.
See also
Installing SINUMERIK products (Page 77)
PCU-Basesoftware (IM8)
8 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.1 Delivery condition of the system
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 9
Commissioning the system
1.1 Delivery condition of the system
See also
This is how you set the IP address of the PCU (Page 45)
References: Operator Components and Networking Manual
PCU-Basesoftware (IM8)
10 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.2 User administration
Preset users
Each user is from one user type and belongs to one user group. The user types are
implemented under Windows in user groups with various user rights.
Upon delivery of the system, the following users are defined at the factory:
● The "operator"
In terms of type, the "operator" is classed as an HMI user and belongs to the operators'
user group (operator.group). These operators have limited user rights under Windows.
● The "user"
In terms of type, the "user" is classed as an HMI user and belongs to the operators' user
group (user.group). These operators have extended user rights under Windows.
● The "auduser".
The "auduser" is an HMI service user type of user and belongs to the system
administrators' user group. The system administrators have the user rights of a local
administrator under Windows.
User name Password User type Windows user User Rights User group
group
operator operator HMI (operator.group) operator.group Restricted Operator
user CUSTOMER HMI (user.group) user.group "Power User" Operator
auduser SUNRISE HMI+Service Administrators local System administrators
administrator
siemens ***** --- --- --- System administrators
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 11
Commissioning the system
1.2 User administration
Service Desktop
The service desktop provides the HMI+Service user with a Windows desktop, which is
expanded to include tools and functions for service tasks, such as manage users, install
software, save/restore data, check system integrity, etc.
Windows desktop
The HMI user is able to use a Windows desktop which can be expanded to suit his or her
individual needs.
PCU-Basesoftware (IM8)
12 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.2 User administration
"Global Settings"
In the ServiceCenter Users, as HMI service user, you set parameters under "Global
Settings" for the system behavior:
● When the PCU is booting up
● When the HMI program is starting
● With reference to the desktop
Note
The following diagrams show, as an example, an application with the
SINUMERIK Operate software installed.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 13
Commissioning the system
1.2 User administration
PCU-Basesoftware (IM8)
14 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.2 User administration
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 15
Commissioning the system
1.2 User administration
PCU-Basesoftware (IM8)
16 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.2 User administration
"HMI" tab
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 17
Commissioning the system
1.2 User administration
PCU-Basesoftware (IM8)
18 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.2 User administration
Principle of passing on
The settings made under "Global Settings" are passed on to individual users. The settings
which are passed on can still be adapted to suit each user.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 19
Commissioning the system
1.2 User administration
PCU-Basesoftware (IM8)
20 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.2 User administration
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 21
Commissioning the system
1.2 User administration
See also
How to add the PCU to a domain (Page 47)
Overview
As an HMI+Service user, you can execute the following tasks in the Users ServiceCenter:
● Change user names.
● Delete users.
Deleting a user
To delete a user again, follow these steps:
1. Left or right-click the user who you wish to delete in the list.
2. To delete the user, select "Delete" from the short-cut menu using righthand mouse key.
Result: The user is deleted after confirming the confirmation prompt.
PCU-Basesoftware (IM8)
22 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.3 Boot up behavior of the PCU
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 23
Commissioning the system
1.3 Boot up behavior of the PCU
Note
If an HMI program is installed, the "Start HMI" button is also available in the "Desktop
Access" dialog.
PCU-Basesoftware (IM8)
24 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.3 Boot up behavior of the PCU
Note
Setting the access level via EKS
If an EKS unit is available, the following behavior applies:
• If an EKS unit is active, i.e. the key is inserted and can be evaluated, then the key
information for the EKS unit alone determines the active access level. The access
level in the HMI program cannot be changed when EKS is active.
• If the key is withdrawn from the active EKS unit, i.e. the EKS unit becomes inactive,
the system adopts the current access level as determined by the key switch.
• If changing the operating right amongst the operating stations, the EKS unit of the
new active operating station is authoritative. If no EKS unit is assigned there, the
effect is the same as for an inactive EKS unit.
• The key information is evaluated by the HMI. Once an access level has been
determined from the key information, HMI adopts this access level and also sets it
in the NCK: The last access level set always applies to the system.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 25
Commissioning the system
1.3 Boot up behavior of the PCU
Requirement
No HMI program is installed during the PCU boot up.
Ramp-up phase
Explanations:
PCU-Basesoftware (IM8)
26 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.3 Boot up behavior of the PCU
● If installation programs are present in directory D:\Install, you will be prompted during the
first boot up as to whether the installation procedure should be started. After installation is
completed, you need to restart the system.
The installation can also be skipped and carried out later. To do this, use the HMI
Explorer (Installation via service desktop (Page 78)).
● "Desktop", "ServiceCenter Users" or "Shutdown" can be selected in the dialog
"Desktop Access".
– When selecting "Desktop", the "Desktop Logon" dialog is opened.
– When selecting "ServiceCenter Users", the "Installing Logon" dialog is opened.
Note
When booting the PCU for the first time, the user can only log on as 'auduser'.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 27
Commissioning the system
1.3 Boot up behavior of the PCU
Requirement
There is already an HMI program installed.
Ramp-up phase
PCU-Basesoftware (IM8)
28 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.3 Boot up behavior of the PCU
Explanations:
● If the HMI program is already installed, the PCU boots up and the HMI program is started
(default).
● During the boot up, there is a time interval for pressing key <3> when the version
information appears on the lower right of the background screen. Then the
"Installing Logon" dialog opens.
● To carry out service tasks, you will have to log on as a service user.
The following input options are available:
– Manual logon to a domain using user name and password.
– Logon using EKS: A key and valid user data for authentication must be provided for
this. If valid user data is not available via the EKS, the "Desktop Logon" dialog is
displayed along with user name and password.
– Both options can be selected.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 29
Commissioning the system
1.3 Boot up behavior of the PCU
Overview
The system behavior during boot up for the screen resolution is set in the file tcu.ini. You will
find the delivery status for tcu.ini in E:\siemens\system\etc.
Modified tcu.ini files are saved in F:\addon_base\..., F:\oem_base\..., F:\user_base\...
Reference: Operator Components Manual, "Networking" chapter
Settings Meaning
SYSTEM The resolution is not specially set; i.e., the resolution last used in the
system is active, e.g., the resolution which had been set manually in the
Control Panel.
AUTO_OP_1 Default:
During boot up, the resolution is automatically set ("PCU panel" has priority)
in accordance with the following scenarios:
Example 1: There is a PCU panel (irrespective of whether there is a PCU monitor and
TCU panels)
[in active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU panel
(max. 1280x1024).
PCU-Basesoftware (IM8)
30 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.3 Boot up behavior of the PCU
Settings Meaning
Example 2: There is no PCU panel, however there is a PCU monitor (irrespective of
whether there are any TCU panels):
[in active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is not specially set; i.e., the resolution last used in the
system is active, e.g., the resolution which had been set manually in the
Control Panel.
(Different to AUTO_OP_2 !)
AUTO_OP_2 Like AUTO_OP_1, except:
Example 2: There is no PCU panel, however there is a PCU monitor
(irrespective of whether there are any TCU panels):
[in active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU monitor, reduced to
the next lowest SINUMERIK resolution. The SINUMERIK resolutions are
640x480, 800x600, 1024x768 and 1280x1024.
Example: In the case of a PCU monitor with a max. resolution of 1440x900,
the SINUMERIK resolution setting is 1280x1024.
AUTO_MON_1 During boot up, the resolution is automatically set ("PCU monitor" has
priority) in accordance with the following scenarios:
Example 1: There is a PCU monitor (irrespective of whether there is a PCU panel and
TCU panels)
[in active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU monitor, reduced to
the next lowest SINUMERIK resolution. The SINUMERIK resolutions are
640x480, 800x600, 1024x768 and 1280x1024.
Example: In the case of a PCU monitor with a max. resolution of 1440x900,
the SINUMERIK resolution setting is 1280x1024.
If there is a PCU panel, the display there is panned if the max. resolution of
the PCU panel is lower than the max. resolution of the PCU monitor.
Example 2: There is no PCU monitor, however there is a PCU panel (irrespective of
whether there are any TCU panels):
[in active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is not specially set; i.e., the resolution last used in the
system is active, e.g., the resolution which had been set manually in the
Control Panel.
(Different to AUTO_MON_2 !)
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 31
Commissioning the system
1.4 BIOS settings for PCU 50.3
Settings Meaning
Example 3: There is no PCU monitor and no PCU panel (= headless operation):
A) in active TCU mode:
a) dynamic resolution switching is enabled (resolution adaptation entry in
TCU.ini) and at least one TCU is already logged on:
The resolution is set to the resolution of the TCU which is currently active.
b) dynamic resolution switching is enabled (resolution adaptation entry in
TCU.ini) and no TCU has logged on yet or dynamic resolution switching is
disabled:
The resolution is set to the max. resolution of the current PCU panel, i.e.,
which logged on during the previous session.
Default: Default TCU resolution in accordance with the registry.
Notice: The first TCU panel to logon (later) becomes activated. The focus
handler then automatically sets the resolution to this TCU panel's resolution
(in the case of dynamic resolution switching).
A) in inactive TCU mode:
The resolution is not specially set - i.e. the resolution used during the
previous session in the system is active, e.g. the resolution set manually in
Control Panel.
AUTO_MON_2 Like AUTO_MON_1, except:
Example 2: There is no PCU monitor, however there is a PCU panel
(irrespective of whether there are any TCU panels):
[in active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU panel
(max. 1280x1024).
640X480 During boot up, the SINUMERIK resolution is set to 640x480.
800X600 During boot up, the SINUMERIK resolution is set to 800x600.
1024X768 During boot up, the SINUMERIK resolution is set to 1024x768.
1280X1024 During boot up, the SINUMERIK resolution is set to 1280x1024.
PCU-Basesoftware (IM8)
32 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.4 BIOS settings for PCU 50.3
Overview
The BIOS of the PCU is preset in such a way that no changes are required. The date and
time can be set under Windows or the user interface.
Note
Changes in the BIOS
Your device configuration is preset for working with the software supplied with the unit.
You should only change the preset values if you have modified your device in any way, or if
a fault occurs when the unit is powered up.
2. Press the F2 key as long as the BIOS prompt appears on the screen.
The BIOS main menu opens:
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 33
Commissioning the system
1.4 BIOS settings for PCU 50.3
Boot options
Quick boot mode Enabled
SETUP prompt Enabled
POST errors All, but not keyboard
Summary screen Enabled
Diagnostic screen Enabled
Post Code/Status LPC Bus
Keyboard features
Numlock ON
Key click Disabled
Keyboard auto-repeat rate 30 / sec
Keyboard auto-repeat delay ½ sec
Hardware options
PCI MPI/DP Enabled
Onboard Ethernet 1 Enabled
On-board Ethernet 1 Address 08 00 06 90 xx xx
On-board Ethernet 1 Remote Boot Enabled
Onboard Ethernet 2 Enabled
On-board Ethernet 2 Address 08 00 06 90 xx xx
On-board Ethernet 2 Remote Boot Disabled
SafeCard functions Enabled
PCU-Basesoftware (IM8)
34 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.4 BIOS settings for PCU 50.3
Hardware options
Fan control Enabled
CRT/LCD selection Simultan. Auto
Menu: Advanced
PCI Configuration
PCI device slot 1
Option ROM scan Enabled
Enable master Enabled
Latency timer Default
PCI device slot 2
Option ROM scan Enabled
Enable master Enabled
Latency timer Default
SATA/PATA Configuration
PATA Controller: Enabled
SATA Controller mode Enhanced
AHCI Configuration Disabled
RAID support Disabled
Menu: Security
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 35
Commissioning the system
1.4 BIOS settings for PCU 50.3
Menu: Boot
Menu: Version
Menu: Exit
Save Changes & Exit All changes are saved; a system restart is carried out with the
new parameters.
PCU-Basesoftware (IM8)
36 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.4 BIOS settings for PCU 50.3
Note
Changes to the BIOS settings, with the exception of the boot sequence, require an OEM
contract to be concluded.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 37
Commissioning the system
1.5 BIOS settings for PCU 50.5
Overview
The BIOS of the PCU is preset in such a way that no changes are required. The date and
time can be set under Windows or the user interface.
Note
Changes in the BIOS
Your device configuration is preset for working with the software supplied with the unit.
You should only change the preset values if you have modified your device in any way, or if
a fault occurs when the unit is powered up.
2. Press the F2 key as long as the BIOS prompt appears on the screen.
The BIOS main menu opens:
PCU-Basesoftware (IM8)
38 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.5 BIOS settings for PCU 50.5
Menu: Main
Menu: Advanced
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 39
Commissioning the system
1.5 BIOS settings for PCU 50.5
Menu: Security
PCU-Basesoftware (IM8)
40 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Commissioning the system
1.5 BIOS settings for PCU 50.5
Menu: Power
Menu: Boot
Menu: Version
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 41
Commissioning the system
1.5 BIOS settings for PCU 50.5
Menu: Exit
Note
Changes to the BIOS settings, with the exception of the boot sequence, require an OEM
contract to be concluded.
Boot sequence
BIOS version 05.01.12
In order to ensure correct functioning of the Software Ghost with Backup/Restore, please set
in BIOS under "SATA/PATA Configuration" → "SATA Controller Mode" → "Compatible".
The CompactFlash Card is entered as SATA. The hard disk (or Solid State Drive) is DISK0,
and the CompactFlash Card is DISK2.
PCU-Basesoftware (IM8)
42 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system 2
2.1 System settings
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 43
Configuring the system
2.1 System settings
Default
The PCU is supplied with an automatically generated computer name.
Procedure
To change the name of the PCU:
1. Select "Start" → "Control Panel" → "System".
2. Select the "Computer Name" tab and click on "Change".
The following dialog opens:
PCU-Basesoftware (IM8)
44 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.1 System settings
Default setting
Note
IP address in the system network
The IP address 192.168.214.241 is set as a factory default for every PCU on the system
network.
You must only perform the steps described below if you wish to change this default.
Procedure
1. Select the following on the PCU on the Service Desktop: "Start" → "Settings" → "Network
Connections".
The "Network Connections" window opens.
2. Double-click the Ethernet 2 interface you want to parameterize which is to be used for
connecting the TCU or system network.
The "Ethernet 2 (System Network) Properties" window opens.
3. Under the "General" tab, select "Internet Protocol (TCP/IP)" and click the "Properties"
button.
The "Internet Protocol (TCP/IP) Properties" window opens:
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 45
Configuring the system
2.1 System settings
4. Under the "General" tab, select the "Use the following IP address" option and enter the IP
address and the subnet screen form.
Recommended setting for the first PCU:
5. Enter the required new IP address and confirm the settings with "OK".
PCU-Basesoftware (IM8)
46 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.1 System settings
Requirement
Only a user with the corresponding entitlement, e.g. a domain administrator, can add a PCU
to an existing domain.
Proceed as follows
To add the PCU to a domain:
1. Select: "Start" → "Settings" → "Control Panel" → "System", "Computer Name" tab.
Default: The PCU belongs to a "WORKGROUP" and is not assigned to any domain.
2. Click "Change ...".
The following dialog opens:
3. Enter the name of the domain to which you want to add the PCU.
4. You will then be asked to log on as a user with the corresponding entitlement to conclude
the process.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 47
Configuring the system
2.1 System settings
Preconditions
To connect an external monitor, the following preconditions apply:
● The external monitor is connected to the DVI interface on the PCU (using an adapter, if
necessary).
● The monitor may not be connected while in use.
Procedure
To connect an external monitor:
1. Right-click the PCU's service desktop and select "Properties" from the pop-up menu.
2. Select the "Settings" tab and then click "Advanced".
3. Select the "Troubleshooting" tab and and set the "Hardware acceleration" to a value other
than zero. The recommended setting is "full".
4. Close the dialog and click OK to confirm all the dialogs.
5. Repeat steps 2 and 3. There is an additional tab for "Intel(R) ... Grafics Controller"
6. Click the "Graphics Properties" button.
– In the case of a PCU 50.3: On the "Devices" tab the external monitor corresponds to
the "Monitor" selection; the OP/TP on the PCU corresponds to the "Notebook"
selection. Select a "Primary Device" and a "Secondary Device".
– In the case of a PCU 50.5: On the "Display" tab, the OP/TP on the PCU corresponds
to the selection "Primary Display"; the external monitor corresponds to the selection
"Secondary Display". Click the button "Multiple Displays" to select the "Clone" or
"Extended" mode.
7. Close the dialog and click OK to confirm all the dialogs: The external monitor is now
ready.
PCU-Basesoftware (IM8)
48 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.1 System settings
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 49
Configuring the system
2.2 Configuring a customized operator interface
Default setting
In the delivery condition, the Windows XP operating system is only installed on the PCU in
English and with a US keyboard layout.
Requirement
In order to be able to switch languages, the desired languages must be installed from the
DVD of the "SINUMERIK Service Pack Recovery Media Win XP ProEmbSys SP2". With the
"Multilingual User Interface" (MUI), you can switch to menus, dialog boxes and keyboard
layouts for the Windows system in different languages:
WARNING
"Regional Options" tab
The settings for the keyboard assignment and the formats for date, time and number
displays on the "Regional Options" tab must not be changed under "Standards and
formats".
These settings are automatically adapted depending on the language selected for the
operating software.
PCU-Basesoftware (IM8)
50 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.2 Configuring a customized operator interface
Select a language
After installing a language from the corresponding CD, proceed as follows:
1. Select "Start" → "Control Panel" → "Language and Regional Options", to open the
following dialog box:
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 51
Configuring the system
2.2 Configuring a customized operator interface
2. Select the "Languages" tab, in order to switch the language for the Windows XP user
interface. Under "Language used in menus and dialogs," select the new language and
confirm with OK.
3. On the "Advanced" tab, select the language for programs that do not support Unicode.
Result
To make the language change effective, the PCU must be rebooted. The selectable
languages are displayed using the font set of the respective language.
See also
How to install additional languages under Windows XP (DVD) (Page 84)
PCU-Basesoftware (IM8)
52 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.2 Configuring a customized operator interface
Default setting
The Siemens boot screen is archived in the PCU under the following path:
F:\hmisl\siemens\sinumerik\hmi\ico\ico640\splash.png
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 53
Configuring the system
2.2 Configuring a customized operator interface
Procedure
Background picture
1. Save the required pictures in the appropriate resolutions in the corresponding subfolders
of F:\Background picture
2. Switch to the appropriate "User Types" in the ServiceCenter Users and specify the
F:\Background picture folder at "Background" in the "Desktop" tab.
Note
An attempt to set the Service Desktop background (as in standard Windows) via the Control
Panel does not affect the Service Desktop background display, but only the startup screen
display.
Background pattern
A background pattern for the Service Desktop is not set via the "Control Panel" (system
control), but in the registry:
Key: HKLM\SOFTWARE\Siemens\SINUMERIK\Basesoftware\
<version>\HMIDesktop
Value: Pattern (STRING)
Date: <bit code>" (e.g. "0 80 114 32 0 5 39 2",
see HKCU\Control Panel\Patterns)
"(None)" (= NO background pattern)
InitDatum: Background pattern previously set via the Control Panel
Default data: "(None)" (if entry is not available/readable)
PCU-Basesoftware (IM8)
54 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.3 Customized settings during boot up
Overview
Regarding the settings and functionality, booting followed by the start of an HMI program
starting differs from booting with subsequent start of the Service Desktop.
Filtering keys
During boot up of an HMI program, keystroke sequences and pressed function keys are
simultaneously filtered. The keystroke sequences and functions that were pressed
simultaneously and are to be filtered are configured in file E:\Windows\System.ini.
Filtering keystroke sequences:
Section: MMC103Keyb
Key: SeqAct
Value: <bit mask>
(= keystroke sequences to be filtered, specified in accordance with the comment
in E:\Windows\System.ini)
Init value: 262143
Section: MMC103Keyb
Key: ConcurrentKeyMask
Value: <bit mask>
(= function keys to be filtered, specified in accordance with the comment in
E:\Windows\System.ini)
Init value: 255
In the ServiceCenter Users, the keys that are to be filtered can be configured for each
specific user:
● while the system boots → "Startup (2)" tab
● while the HMI program runs: → "HMI" tab
● on the Service Desktop or Windows Desktop: → "Desktop (2)" tab
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 55
Configuring the system
2.3 Customized settings during boot up
system.ini file
# -------------------------------------------
# SIEMENS KEYBOARD-DRIVER SECTION (START)
# -------------------------------------------
# State of driver after startup
# (0=NORMAL, 1=PERMANENT-SHIFT ACTIVE)
keybStartState=0
PCU-Basesoftware (IM8)
56 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.3 Customized settings during boot up
SeqAct=262143
Note
Scope of the keys
Only keys, which have already been defined in the system.ini file, can be enabled.
No additional keys can be defined for filtering.
See also
ServiceCenter Users: User settings (Page 13)
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 57
Configuring the system
2.3 Customized settings during boot up
The key is effective for all service users and other users.
Links on the service desktop are always saved, irrespective of the registry entry.
Note
Application windows that are still open before logging out, must be closed by the setting
"Save settings" before exiting the service desktop. Otherwise, these application windows will
briefly be displayed and then closed again during a restart immediately before the HMI
program starts.
PCU-Basesoftware (IM8)
58 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.3 Customized settings during boot up
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 59
Configuring the system
2.3 Customized settings during boot up
Overview
You can start OEM programs directly before starting the HMI system software. This requires
these programs (or their links) to be stored in subdirectories of the directory C:\RunOEM.
Starting sequence
The subdirectories are executed in the order listed. The programs within a subdirectory are
started in the chronological order in which they were placed in the subdirectory.
● Programs in the C:\RunOEM\SeqOnce subdirectory are started once and sequentially,
i.e., a program is not started until the previously started program is completed.
● Programs in the C:\RunOEM\Seq subdirectory are started sequentially whenever the
system is ramped up, i.e., a program is not started until the previously started program is
completed.
● Programs in the C:\RunOEM\ParOnce subdirectory are started once and simultaneously.
They run parallel with the HMI system software.
● Programs in the C:\RunOEM\Par subdirectory are started simultaneously whenever the
system is ramped up. They run parallel with the HMI system software.
Not only program files, but also other types of file can be stored in the subdirectories, which
are then opened in accordance with their file type.
For example, ".txt" files are opened using Notepad, ".htm" files are opened using Internet
Explorer.
PCU-Basesoftware (IM8)
60 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.3 Customized settings during boot up
[OEMRunOnce]
"Check Password","x:\I386\system32\CheckPEPwd.exe"
[OEMRun]
"notepad","e:\windows\notepad.exe"
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 61
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
2.4 Configuring the SITOP UPS module for use with the PCU Base
Software
Overview
SITOP UPS modules can continue operation of the PCU 50.5 temporarily if a power failure
occurs and/or shut down the system properly.
For example, a SITOP UPS module also protects against data loss when the PCU 50.5
hardware is shut down, because for technical reasons with Windows-based systems, data is
still written to the SSD after shutdown.
● You will find general information about SITOP UPS modules used in combination with the
PCU base software in Section SITOP modules for the PCU 50.5 (Page 62).
● If you want to use a SITOP UPS module in combination with the PCU base software, you
must first adapt the settings of the SITOP software (Page 64).
● Optionally, you can adapt the delay time after which the HMI software will be forced to
shut down (Page 67).
● You must configure the hardware (Page 69) of the SITOP UPS module before using it
with the PCU base software.
PCU-Basesoftware (IM8)
62 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
Further information
Information about available SITOP UPS modules is given in the catalog or in the Internet:
● Catalog KT 10.1 Power supply SITOP
● SIEMENS Industry Mall > 24 V DC Uninterruptible Power Supplies
(https://eb.automation.siemens.com/mall/en/US/Catalog/Products/7010117)
Note
Information about the test environment for machine OEMs
The functionality has been tested in the standard configuration with the PCU base software.
When installing add-on or OEM software components, you must check the shutdown
procedure of the entire system and adapt the factory setting (180 seconds).
See: Parameterizing a delay time for quitting the HMI software (Page 67)
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 63
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
Requirement
● The SITOP UPS hardware is connected via the USB interface.
● The SITOP software of version 3.x.2.16 or later is installed in directory C:\Program Files
(x86)\SITOP\
● If you want to use SITOP software of version 3.2.1.16 or older, this must be installed as a
normal application, not as a service.
Note
Windows service of the SITOP software version 3.2.1.16 or older is not compatible with
the PCU base software
If you use SITOP software of version 3.2.1.16 or older as a Windows service with the
PCU base software, the correct shutdown procedure cannot be performed!
If you have installed the SITOP software of version 3.2.1.16 as a Windows service, you
must uninstall this and install it again as an application in order to be able to use it in
conjunction with the PCU base software.
As of version 3.2.1.17, the SITOP software can be used as service with the PCU base
software and is recommended.
● The SITOP software was configured during the installation so that it starts automatically
when Windows is run-up (factory setting).
● The Service Desktop is active.
PCU-Basesoftware (IM8)
64 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
Procedure
Proceed as follows to configure the SITOP software for use with the PCU base software:
1. Call the settings of the SITOP software, for example, by right-clicking the SITOP UPS
icon in the Windows information area and then selecting "Configuration".
The "SITOP DC UPS Configuration" dialog box opens.
2. In the "General" tab, select "UPS" in the drop-down list at "Serial interface".
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 65
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
3. Switch to the "Floating operation" tab and make the following settings:
– Deactivate the "Display monitoring window after" checkbox
Note
Deactivating the monitoring window
Display of the monitoring window can cause malfunctioning of the HMI software.
– Click directly in the text field at "Start application after" and specify the path of the
Shutdown.bat:
C:\Program Files
(x86)\Siemens\MotionControl\siemens\sinumerik\hmi\base\Shutdown.bat
Note
Do not use the "Browse" button
The dialog can crash if you use the "Browse" button to specify the path of the
Shutdown.bat.
– After you have specified the path of the Shutdown.bat, activate the "Start application
after" checkbox. Optionally, you can specify the wait time after which the Shutdown.bat
is to be executed (e.g. 5 seconds).
PCU-Basesoftware (IM8)
66 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
Note
Information about the test environment for machine OEMs
The "SITOP UPS" function has been tested in the standard configuration with the PCU base
software. When installing add-on or OEM software components, you must check the
shutdown procedure of the entire system and adapt the factory setting.
Requirement
● The SITOP UPS module is configured for use with the base software.
See Configuring SITOP software for PCU Base Software (Page 64).
● The Service Desktop is active.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 67
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
Procedure
Proceed as follows to change the delay time:
1. Call the settings of the SITOP software, for example, by right-clicking the SITOP UPS
icon in the information area and then selecting "Configuration".
2. In the "SITOP DC UPS Configuration" dialog box, enter the wait time in seconds as a
command line parameter in the "Floating operation" tab:
– Syntax: <Path>\Shutdown.bat -<Time in seconds>
– Example: C:\Program Files
(x86)\Siemens\MotionControl\siemens\sinumerik\hmi\base\Shutdown.bat -180
PCU-Basesoftware (IM8)
68 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
Buffering parameterization
The UPS module can be used to select whether buffering should be completed after a
predetermined period of time or not until the accumulator’s lowest discharge threshold (=
maximum buffer time) has been reached. Both buffering parameterizations result from this.
On - Off
1 +2V
Cut-in threshold
2 +1V +22V fixed
3 +0.5V
4 +1V
7 +0.2V
8 +0.2V
9 +0.1V
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 69
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
On - Off
1 Set time/max. time
2 +320 s
4 +80s
5 +40s +5 s fixed
6 +20s
7 +10s
8 Disconnection
Legend:
Delivery condition setting
PCU-Basesoftware (IM8)
70 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
On - Off
1 +2V
Cut-in threshold
2 +1V +22V fixed
3 +0.5V
4 +1V ∘
∘
5 +1V End-of-charge voltage
+ 26.3V fixed
6 +0.5V
7 +0.2V
8 +0.2V
9 +0.1V
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 71
Configuring the system
2.4 Configuring the SITOP UPS module for use with the PCU Base Software
On - Off
1 Set time/max. time
2 +320 s ∘
∘
3 +160s Buffer time
+5 s fixed
4 +80s
5 +40s
6 +20s
7 +10s
8 Disconnection
Legend:
Delivery condition setting
PCU-Basesoftware (IM8)
72 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.5 Configuration of the Service Center
2.5.1 Overview
You can permanently adapt the settings for the backup and restoration of disk images
(Service Center (Page 87) component) in the "Service Center Backup/Restore" dialog box:
● Configuration of the network adapter (Page 74)
● Configuration of the host (Page 76)
Adaptations that you make here are stored in the servicesystem.ini configuration file.
You can also adapt the settings directly in the associated configuration files:
● servicesystem.ini
● Additional settings for the Service System on the USB flash drive: ghost.ini
You can also view the log files of the Service Center or restart the PCU 50.5 in the Service
Center in the "Service Center Backup/Restore" dialog box.
To open the dialog box, click the ServiceCenter Backup-Restore icon on the Desktop.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 73
Configuring the system
2.5 Configuration of the Service Center
Overview
You can make the following IP settings in the "Adapter Settings" dialog box:
Settings Purpose
Adapter Select the Ethernet interface that you want to configure.
All settings in this dialog box refer to the selected Ethernet interface.
Use Windows Settings Select whether the values set in the Control Panel are to be used.
Obtain an IP address automatically Select whether the addresses are to be fetched dynamically from the DHCP server.
(DHCP) If the checkbox is deactivated, you must make the settings manually.
IP Address Set the IP address of the NCU.
You can specify an IP address from the following range:
192.168.214.250 - 254
Subnet Mask Specify a subnet mask, e.g. 255.255.255.0
PCU-Basesoftware (IM8)
74 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Configuring the system
2.5 Configuration of the Service Center
Settings Purpose
Default Gateway Set the IP address of the standard gateway.
A standard gateway creates a standard route in the IP routing table for all destinations that are
not in the subnet.
Name Server Set the IP address of the name server.
A name server answers questions asked about a domain name zone using a DNS database.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 75
Configuring the system
2.5 Configuration of the Service Center
Overview
You can make the following settings in the "Network Settings" dialog box:
Settings Purpose
Network enabled Activate or deactivate the network interfaces of the PCU 50.5.
Firewall enabled Activate or deactivate the firewall of the PCU 50.5.
Use Windows Settings Select whether the values set in the Control Panel are to be used.
DNS Configuration > Computer Name Specify the DNS computer name.
DNS Configuration > Suffix Search List Parameterize a search list for DNS suffix, e.g. "network.com".
The factory setting of the Ethernet interface "Local Area
Connection" is ".local".
PCU-Basesoftware (IM8)
76 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Install software and updates 3
3.1 Installing SINUMERIK products
Overview
This chapter describes how to install additional software on the basis of the pre-installed
PCE basic software or how to carry out an update.
The description below is based on the delivery condition of the hardware and software
components.
The service desktop is, for example, used for the following tasks:
● Installing HMI system software
● Setting the running environment of the HMI system software
● Checking the hard disk or version
● Privilege for SIMATIC STEP 7
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 77
Install software and updates
3.2 Installation via service desktop
PCU-Basesoftware (IM8)
78 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Install software and updates
3.2 Installation via service desktop
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 79
Install software and updates
3.2 Installation via service desktop
PCU-Basesoftware (IM8)
80 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Install software and updates
3.2 Installation via service desktop
● Component information
The "Components" dialogue box shows the information on the components
accompanying a product:
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 81
Install software and updates
3.3 How to install and authorize SIMATIC STEP 7
Overview
SIMATIC STEP 7 V5.5 SP1 can also be installed on the PCU.
Note
The "MPI driver" package available on the PCU is part of the HMI software and must not be
uninstalled!
A network connection or a connection to a DVD drive is required.
Recommendation: Mouse port
PCU-Basesoftware (IM8)
82 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Install software and updates
3.3 How to install and authorize SIMATIC STEP 7
5. Switch to the Sinumerik_Add_on directory on the DVD and call SETUP.EXE. The
installation proceeds with operator prompting. Once installation is complete, the PC will
need to be rebooted. During boot up, select the service desktop again.
6. Start the link "STEP7 authorizing" on the service desktop. This authorizes STEP 7 and it
can be started from the operating software (STEP 7 appears as its own operating area on
the expansion bar of the area menu, protected with access level 3).
The following entries are made automatically in F:\Add_on\oemframe.ini:
[s7tgtopx]
WindowStyle_Off=196608
nSwitchToTaskAfterTermination= -2
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 83
Install software and updates
3.4 How to install additional languages under Windows XP (DVD)
Use
Use the SINUMERIK service pack recovery media WIN XP ProEmbSys SP3 to:
● Subsequently install Windows components
● Re-establish the delivery condition of the PCU without application software
● To install other languages for Windows XP
Directory Contents
1_WIN_Components Windows XP ProEmbSys SP3
Windows XP ProEmbSys operating system, incl. SP3 for post-
installation of software components that are no longer located on
the PCU.
2_XP_Base Symantec Ghost image for PCU 50.3 and EBOOT
• Ghost image of the delivery condition of the PCU basic
software Windows XP for PCU 50.3 without application
software.
• Ghost image for creating an "Emergency Boot System"
(identical to the directory D:\EBOOT on the PCU)
3_MUI_1 Chinese (simplified)
Traditional Chinese
Japanese
Korean
Romanian
Slovakian
4_MUI_2 Danish
German
French
Dutch
Italian
Spanish
Swedish
PCU-Basesoftware (IM8)
84 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Install software and updates
3.4 How to install additional languages under Windows XP (DVD)
Directory Contents
5_MUI_3 Brazilian Portuguese
Finnish
Polish
Russian
Czech
Turkish
Hungarian
EULA TERMS Contained
Certificate of authenticity Not contained
Installing languages
To install additional languages, proceed as follows:
1. If no DVD drive is directly connected via a USB port, the DVD can be accessed via a
network to a released DVD disk drive via "Explorer" → "Tools" → "Map Network Drive".
The letter G should be selected as the drive letter.
2. Select the directory with the appropriate language, the program "MUISETUP.EXE" starts.
After accepting the licensing conditions, you can start the installation procedure with
"Continue". A list of all of the pre-installed languages and the languages available on the
DVD is displayed.
3. Now the desired languages can be installed/uninstalled by inserting or deleting a check
mark in front of the language.
4. Other settings include:
– Choice of language version for the standard user/new user
– The language for programs without Unicode support must be set to "English (US)".
– The font set must also be set to "English (US)".
5. After confirming with "OK," the installation begins. Many languages (e.g. Chinese) require
system files that are also located on the DVD.
If the installation drive is other than the recommended "G:" the "Windows XP Professional
Service Pack 2 CD" or the "Windows XP Professional CD" may be required. The path
name must then be changed accordingly.
6. After successful installation, a reboot may be requested depending on the language.
Note
• The choice can only be made from among the languages that were previously
installed on the PCU.
• The new language of Windows XP only goes into effect if the user logs in again after
the changeover or the PCU is turned off and then on again.
• The language setting of the operating software is independent of this. It is set
independently of this under "Start-up" → "HMI" → "Change Language".
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 85
Install software and updates
3.4 How to install additional languages under Windows XP (DVD)
PCU-Basesoftware (IM8)
86 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data 4
4.1 Overview
You can perform installation and commissioning work on the PCU in theService Center,
which is based on Microsoft Windows PE.
When the Desktop is active, configuration of the Service Center is possible via the
"ServiceCenter Backup-Restore" (Page 73) icon.
Most of the functions of the Service Center are available in the main menu (Page 88).
In particular, you can create or restore disk images in the Service Center. The following
options are available:
● Create a disk image of the SSD (Page 93)
● Restore a disk image of the SSD (Page 95)
● Create a disk image of a partition (Page 97)
● Restore a disk image of a partition (Page 99)
The Service Center uses the Symantec Ghost (Page 104) software, which you can also call
separately.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 87
Backing up and restoring data
4.3 Functions of the Service Center
Overview
In the upper section of the Service Center main menu, you can select one of five tasks.
Buttons for additional functions are available in the lower section.
PCU-Basesoftware (IM8)
88 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.3 Functions of the Service Center
Note
Data backup and restore with CompactFlash cards
If there is a CompactFlash card in the slot of the PCU, you will not be able to back up or
restore data via the Service Center.
Instead, start the "ghost32.exe" program via the prompt of the Service Center.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 89
Backing up and restoring data
4.4 Network settings in the Service Center
Note
Temporarily storing network settings in the Service Center
Any network settings you make in this dialog box are immediately effective, but temporary.
To change network settings permanently, switch to the Service Desktop.
For further information, see Section Configuration of the Service Center (Page 73).
PCU-Basesoftware (IM8)
90 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.4 Network settings in the Service Center
Overview
IP settings
You can make the following IP settings in the "Network Settings" dialog box:
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 91
Backing up and restoring data
4.4 Network settings in the Service Center
Routing settings
You can make the following routing settings in the "Network Settings" dialog box:
Settings Purpose
Add Route Add a new route.
Remove Route Delete a selected route.
Destination Specify the network destination of the route as an IP address.
Mask Subnet mask of the specified IP addresses.
Next Next hop or forwarding IP address via which the network destination can be accessed.
Interface Select an interface to which the configured IP routing applies:
• Enterprise network interface X1 (Local Area Connection 2)
• Plant network interface X2 (Local Area Connection)
Metric Integer cost metric (1 to 9999). Required if several routes for sending a packet to a network destination are possible in
the routing table.
See also
Release directory of the PC/PC in the network (Page 114)
Creating a shortcut to the network drive (Page 119)
Configuring routing in the network (Page 109)
PCU-Basesoftware (IM8)
92 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.5 Create a disk image of the SSD
Procedure
To save the SSD as a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Starting the Service Center (Page 87)
2. In the main menu of the Service Center, click "Disk Backup".
The "Service Center - Disk Backup" dialog box opens.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 93
Backing up and restoring data
4.6 Restore a disk image of the SSD
4. Confirm your settings with "Backup" to start generation of the disk image.
PCU-Basesoftware (IM8)
94 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.6 Restore a disk image of the SSD
Note
Restoring replaces all current files
When you restore the PCU from a disk image, all programs, settings, and files are
completely replaced by the disk image. You cannot restore individual files or exclude
individual files from restoration.
Requirement
A disk image exists
See: Create a disk image of the SSD (Page 93)
Procedure
To restore a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Starting the Service Center (Page 87)
2. In the main menu of the Service Center, click "Disk Restore".
The "Disk Restore" dialog box opens.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 95
Backing up and restoring data
4.6 Restore a disk image of the SSD
4. To start the restore process and entirely replace the existing data on the SSD with the
disk image, confirm the settings with "Restore".
Result
The restore process is started.
Note
Troubleshooting if reading in of the disk image fails
If data transfer is interrupted during the restore process, the PCU will have no executable
system.
In this case, use a bootable USB flash drive with Service Center to read the disk image in
again.
PCU-Basesoftware (IM8)
96 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.7 Create a disk image of a partition
Procedure
To save a partition of the SSD as a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Starting the Service Center (Page 87)
2. In the main menu of the Service Center, click "Partition Backup".
The "Service Center - Partition Backup" dialog box opens.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 97
Backing up and restoring data
4.8 Restore a disk image of a partition
4. Confirm your settings with "Backup" to start generation of the disk image.
PCU-Basesoftware (IM8)
98 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.8 Restore a disk image of a partition
Note
Restoring replaces all current files
When you restore a partition from a disk image, all programs, settings, and files are
completely replaced on this partition by the disk image. You cannot restore individual files or
exclude individual files from restoration.
Requirement
A disk image of a partition exists
See: Starting the Service Center (Page 87)
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 99
Backing up and restoring data
4.8 Restore a disk image of a partition
Procedure
To restore a partition from a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Create a disk image of a partition (Page 97)
2. In the main menu of the Service Center, click "Partition Restore".
The "Partition Restore" dialog box opens.
PCU-Basesoftware (IM8)
100 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.8 Restore a disk image of a partition
4. To start the restore process and entirely replace the existing data on the partition with the
disk image, confirm the settings with "Restore".
Result
The restore process is started.
Note
Troubleshooting if reading in of the disk image fails
If data transfer is interrupted during the restore process, the PCU will have no executable
system.
In this case, use a bootable USB flash drive with Service Center to read the disk image in
again.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 101
Backing up and restoring data
4.9 Network settings in the Service Center
Requirement
The network directory is shared with the relevant user accounts in the domain and on the
PCU.
See also: Release directory of the PC/PC in the network (Page 114)
PCU-Basesoftware (IM8)
102 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.9 Network settings in the Service Center
Overview
The setting options in the "Connect a share" dialog box have the following meaning:
Table 4- 4 Settings in the "Connect a Share" dialog box in the Service Center
Further information
You will find information about releasing directories in the network and network drives in the
following sections:
● Release directory of the PC/PC in the network (Page 114)
● Creating a shortcut to the network drive (Page 119)
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 103
Backing up and restoring data
4.10 Starting Symantec Ghost directly
Procedure
To start Symantec Ghost directly, proceed as follows:
1. Call the prompt from the Service Center or the Service Desktop.
2. Enter "ghost.32.exe" and confirm the entry.
Further information
More information is available in the Internet on website Ghost.com (http://www.ghost.com).
PCU-Basesoftware (IM8)
104 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.11 Bootable USB flash drive
Use
You can generate a bootable Service Center (Emergency Boot System) based on Microsoft
Windows PE on a USB flash drive as preventive measure against a defect
The Ghost image is located on the SSD under: D:\Eboot\eboot.gho
Using the same procedure, you can create a Service Center on a PG/PC. For this, Symantec
Ghost must be installed on the PG/PC.
Precondition
● The Windows 7 Service Desktop is active
● You have a USB flash drive (e.g. SIMATIC PC USB flash drive)
Procedure
To create a bootable USD flash drive, proceed as follows:
1. Connect the USB flash drive to a USB interface of the PCU.
2. Start Symantec Ghost, for example, by entering Ghost32.exe in the search bar in the start
menu.
3. In Symantec Ghost, select the "From Image" command from the "Local > Disk" menu.
4. Select D:\Eboot\eboot.gho as the source and the USB flash drive as the destination.
Result
The Emergency Boot System is installed on the USB flash drive and the data medium is
renamed to "EBOOT." The service system on the bootable USB flash drive can now be
used.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 105
Backing up and restoring data
4.12 Operating a service PC/PC in the network
4.12.1 Overview
System network
In the following applications, you will need, for example, a connection between the PCU and
a PG/PC in the system network:
● Save the disk image of the PCU-SSD to a PG/PC
● Restore the SSC of a PCU via the DVD drive of a PG/PC
● Start up the replacement SSD
● Install the software on the PCU via the DVD drive of a PG/PC
Company network
If you want to connect the service PG/PC via a company network (Eth 1), contact your
network service center.
PCU-Basesoftware (IM8)
106 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Overview
The following figures show the typical connection options in the system network:
● PCU to "Eth 2" with service PG/PC, directly, using a crossover Ethernet cable
● PCU to "Eth 2" with service PG/PC, via a switch, using a 1:1 Ethernet cable
Symbol Meaning
Eth 1 as a DHCP client
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 107
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Note
If a PCU is switched off and on again without its own OP/TP including TCU, and if the PCU
boot-up is intended to be performed from the service system (EBS), an external VGA
monitor and keyboard are needed to operate the PCU.
An external VGA monitor and keyboard are not needed if the TCUs are operating and the
PCU is not switched off with the EBS during booting.
Basic procedure
On the PG/PC with Windows 7:
● Connecting a PG/PC to a PCU according to one of the configurations shown above.
● The network protocol used is: TCP/IP.
TCP/IP is already preconfigured on the PCU.
● Setting up IP addresses on the same subnetwork.
● Releasing a directory on the PG/PC for network access.
On the PCU in the Service Center (WinPE):
● On the PCU start the Service Center (WinPE).
● Establish a network connection to the shared directory of the PG/PC.
See: Functions of the Service Center (Page 88)
PCU-Basesoftware (IM8)
108 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Overview
If you have connected a PG/PC at interface X127 of the NCU, configure the network routing
to establish the connection between the PG/PC and the PCU.
Conditions
The following conditions must be met in order to use this function:
● The PG must be connected to interface X127 of an NCU in the system network.
● The NCU and PCU must be connected via the system network.
● On the NCU, the routing is activated in one of the following ways:
– In SINUMERIK Operate 4.5 SP2 or higher, the routing is configured in image "Settings
of the system network".
– In the configuration file basesys.ini, key EnableSysNetToIBNForwarding=1 is set.
● If you wish to access a network directory, it must be shared.
● The user account in question is known to the PG/PC.
● The Service Center is active.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 109
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Procedure
To configure the IP routing in the Service Center, proceed as follows:
1. In the main menu of the Service Center, click "Network".
2. In the "Network Settings" dialog box, click the "IP Routing" tab.
3. Configure the necessary routes. See also: Network settings in the Service Center
(Page 90)
Result
The routing has been configured and the PG/PC and PCU are connected via the NCU.
Now, perform the desired steps, for example, a Restore a disk image of the SSD (Page 95).
PCU-Basesoftware (IM8)
110 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Precondition
● The PG/PC is networked with the PCU in one of the following ways:
– The PG/PC is connected to the PCU with an Ethernet cable (either directly or via a
switch)
See: Connection options in the system network (Page 107)
– The PG/PC is networked with the PCU via an interface on the NCU and the routing is
configured.
See: Configuring routing in the network (Page 109)
● A current Microsoft Windows operating system is installed on the PG/PC
● The PG/PC is switched on
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 111
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Procedure
To configure the network settings of the PG/PC for connecting a PCU in the system network,
proceed as follows:
1. Open the "network connections" window:
– To do this under Windows XP: in the "Start > Control Panel > Network and Internet
Connections" menu, choose "Network Connections."
– To do this under Windows 7: in the Control Panel in category "Network and Internet >
View network status and tasks," choose "Change adapter settings."
2. Right-click on the network adapter you want to configure, then choose "Properties" from
the shortcut menu.
This opens the "Properties of <connection>" dialog box.
PCU-Basesoftware (IM8)
112 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Result
The network settings of the PG/PC are now configured for use with the PCU 50.5.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 113
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Requirement
● The PG/PC is switched on.
● There is sufficient space on the PG/PC for saving, for example, disk images from the
PCU.
● The user accounts to which you want to grant share rights are known in the domain or on
the PCU.
Procedure
Proceed as follows to share a directory for use in the network:
1. On the PG/PC, in the Control Panel call up Computer Management.
2. Under "System > Shared Folders" select the file "Shares."
3. In the "Action" menu, click the "New File Share..." command.
The "Create A Shared Folder Wizard" opens.
PCU-Basesoftware (IM8)
114 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
4. Under step "Name, Description, and Settings," make a note of the Share path, which is a
combination of the computer name and the share name. You will have to specify this
name when you create a link to the network drive on the PCU.
Figure 4-14 Create A Shared Folder Wizard - Name, Description, and Settings
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 115
Backing up and restoring data
4.12 Operating a service PC/PC in the network
5. Under step "Shared Folder Authorizations," select the "Customize authorizations" radio
button, then click "Custom..."
PCU-Basesoftware (IM8)
116 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Figure 4-17 "Select Users, Computers, Service Accounts, or Groups" dialog box
7. In section "Authorizations for <user name>," under column "Allow," click the "Change"
checkbox.
8. Confirm these settings in the "Customize PermiAuthorizations" dialog box with "OK."
9. In the next steps of the wizard, make all the settings you require and confirm the share
with "Finish".
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 117
Backing up and restoring data
4.12 Operating a service PC/PC in the network
4.12.6 Release drives C: and D: of the PCU 50.5 in the network for administrator
accounts
You can release local drives (C$, D$) of the PCU 50.5 in the network for administrator
accounts
You can then access these PCU 50.5 drives, for example from a PG/PC in the network if you
use an administrator user account that is available on the PCU 50.5.
Procedure
1. Enter "regedit" in the search field of the registry.
The registration editor opens.
2. Navigate to the following folder in the folder structure:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Syst
em
3. Right-click in the working area and select the "New > DWORD (32-bit) Value" command
in the shortcut menu.
4. In the "Name" field, enter the "LocalAccountTokenFilterPolicy" designation.
5. Double-click the key and enter "1" as "Value".
6. Confirm the input, close the registration editor and restart the PCU 50.5.
Result
The registry entry has been added and the drives are available in the network after the
restart.
However, you cannot change the access rights, i.e. access is only possible via an
administrator account that is known on the PCU 50.5.
To undo the release, delete the created key in the registration editor.
PCU-Basesoftware (IM8)
118 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Backing up and restoring data
4.12 Operating a service PC/PC in the network
Precondition
● The PG/PC is switched on.
● The PCU is switched on and the Service Desktop is active.
● The folder on the PG/PC is shared for the relevant user accounts on the domain and on
the PCU.
Procedure
Proceed as follows to connect a shared directory as a network drive:
1. Start the Windows Explorer and click the "Map network drive" button.
2. Make the following settings in the "Map network drive" dialog box:
Settings Purpose
Drive To select drive letters under which the network directories are to be
accessible on the PCU 50.5.
Folder Specify the device in the network and share name of the resource.
Syntax: \\Name of the server\share name of the network directory
Example: \\Backup_Server\PCU_Backup
Reconnect at Select this check box to automatically connect the network drive on booting.
logon
Connect using Select this check box if you have not shared the directory in the network with
different the user for whom you would like to set up the network drive.
credentials In the next dialog box "Enter Network Password," enter the log-on
information of a user with whom the network directory is shared.
See also
Microsoft Windows support (http://windows.microsoft.com/en-US/windows/windows-
help#windows=windows-7)
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 119
Backing up and restoring data
4.13 Starting up the replacement SSD
Note
Troubleshooting if reading in of the disk image fails
If reading in of the data is interrupted, the PCU will have no executable system.
In this case, use a bootable USB flash drive with Service Center to read the disk image in
again.
See also
Restore a disk image of the SSD (Page 95)
PCU-Basesoftware (IM8)
120 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics 5
5.1 PCU Hardware Diagnostics
Intended use
The PCU hardware supports the diagnostics of important system components via an
integrated "safecard", which is designated as a Safecard-On-Motherboard (SOM).
These diagnostic functions are only evaluated by systems with HMI Advanced. The fault
statuses of the hardware are reported in the form of alarms via the operator interface of HMI
Advanced. This allows for visualization of the data in HMI Advanced and external evaluation.
Monitored Parameters
The following physical parameters of the PCU hardware are monitored:
● CPU temperature
● Housing temperature
● I/O chip temperature
● Speed of the two housing fans
● S.M.A.R.T - status of the hard disk
Logging faults
The PCU hardware monitor logs all hardware faults in the Windows event log so that the
faults can be output even without installing an HMI application.
The alarms are output in the log under "Control Panel" → "Administrative Tools" → "Event
Viewer".
See also
● Auto-Hotspot
● Operator Components and Networking Manual: Chapter, spare parts
● Description of the alarms: SINUMERIK 840D sl Diagnostics Manual
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 121
Service and diagnostics
5.2 Evaluation of the 7-segment display
Intended use
The 7-segment display is intended for PCU diagnostics in operation without a local OP
(known as "Headless mode"). If an error is detected during booting, a local display is needed
for subsequent error analysis of the connection.
PCU-Basesoftware (IM8)
122 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics
5.2 Evaluation of the 7-segment display
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 123
Service and diagnostics
5.2 Evaluation of the 7-segment display
● During operation:
● During shutdown
PCU-Basesoftware (IM8)
124 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics
5.3 Setting of the service switch (PCU 50.5 only)
Intended use
The "PCU Hardware Service" component as part of the PCU Base software provides a
function to read-out the switch positions.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 125
Service and diagnostics
5.4 Enabling/disabling error log during boot up
Application
Each time the system is booted up, information is written to a block in the file D:\$$Base.log,
which contains the date, time and nature of administrative interventions.
Information about the booting controlled by the HMI Manager, can be displayed on the
screen and written to log file D:\$$Base.log.
InfoLevel (DWORD)
= 1: Mandatory information is output (default setting)
= 2: Mandatory and supplementary information is output
= 3: Mandatory, supplementary and trace information is output
(InfoLevel <= 0 is treated as InfoLevel == 1;
InfoLevel <= 3 is treated as InfoLevel == 3)
ShowInfo (DWORD)
= 0: Displays the mandatory information,
no display of the supplemental and trace information
= 1: Mandatory, supplementary and trace information is displayed (default)
PCU-Basesoftware (IM8)
126 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics
5.5 How to search for stations within the system network
Intended use
The VNC scanner is used within the system network. The scanner is primarily used to
identify devices containing an active VNC server, e.g. NCU or PCU.
The VNC scanner offers the option of connecting directly to the VNC server and, for
example, operating an HMI application. The integrated VNC viewer is used to do this.
Furthermore, it enables you to call up a list of all the network devices, thereby creating an
overview of the system network.
Note
The VNC scanner is available on the Service Desktop of the PCU and on the PCU base
software DVD for installation on a PG/PC.
You require a mouse to use this program.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 127
Service and diagnostics
5.5 How to search for stations within the system network
1. You can launch the "VNC Scanner" program via this link on the Service Desktop of the
PCU .
PCU-Basesoftware (IM8)
128 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics
5.5 How to search for stations within the system network
Note
local device #
When the devices are listed, an IP address will be identified with "#" to indicate that
this is the local device on which the VNC scanner will be used.
2. By right-clicking a network station from the list, you can execute the following actions via
a pop-up menu:
– "VNC": Connecting directly to the VNC server and, if applicable, operating the HMI.
– "VNC → Auto reconnect": Corresponds to the option "Automatic reconnect if the server
closes the connection" in order to restore the connection to the selected network
station.
– Ping: Opens a command shell and executes the "ping" command to the selected
network station.
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 129
Service and diagnostics
5.5 How to search for stations within the system network
Note
Operation via a VNC viewer:
A system can only be monitored from another station via an external VNC viewer
(default).
To view the system from another station, this function must be enabled by the system.
You can find the settings for this in the "System Network Center" or directly in tcu.ini in
the [VNCViewer] section.
Should you wish to access a PCU via the company network using the VNC scanner or
VNC viewer, port 5900 must be added to the PCU under "Control Panel" → "Windows
Firewall" → "Exceptions".
Additional Options
1. Use this button to start the VNC viewer.
2. Use the "Option" button to set parameters for the search.
PCU-Basesoftware (IM8)
130 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics
5.5 How to search for stations within the system network
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 131
Service and diagnostics
5.5 How to search for stations within the system network
NOTICE
Do not change defaults!
To ensure that the VNC viewer works properly, the following options may not be changed.
PCU-Basesoftware (IM8)
132 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Service and diagnostics
5.5 How to search for stations within the system network
After clicking the "Options ..." button, the following dialog opens:
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 133
Service and diagnostics
5.5 How to search for stations within the system network
PCU-Basesoftware (IM8)
134 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
List of Abbreviations A
A.1 Abbreviations
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 135
List of Abbreviations
A.1 Abbreviations
PCU-Basesoftware (IM8)
136 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Index
7 E
7-segment display, 122 Emergency Boot System, 105
Enabling the log, 126
Error log, 126
A
Activating the firewall, 9
G
Global Settings, 13
B
Backup time, 69
H
BIOS
Changing default setting, 37, 42 Hard disk
Start setup, 33, 38 Replacing, 120
System parameters, 34, 39
Boot screen
OEM-specific, 53 M
Storage location, 53
Mains-fed operation, 78
Boot stick, 105
Multilingual User Interface (MUI), 84
C N
Changing computer name, 44
Network
Communication
Adapting settings, 74, 76
MPI, 43
Network release
S7DOS, 43
Drive of the PCU 50.5, 118
Configuration file
Driven on PG/PC, 114
basesys.ini, 109
NTFS file system, 7
ghost.ini, 73
servicesystem.ini, 73, 76
Configuring the user interface, 50
P
Partitioning the hard disk, 7
D Password
For network drive, 102
Dialog box
PCU
ServiceCenter Backup/Restore, 73, 76
Checking the hard disk, 121
Disk image
Delivery condition, 5
Redo, 95, 99
Name (default setting), 9
Troubleshooting, 96, 101
Operating system, 9
Domain, 47
PCU operating system, 9
Driver
Port 80 display, (See 7-segment display)
S7DOS, 43
powerline, 43
PCU-Basesoftware (IM8)
Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0 137
Index
R
Recovery Media, 84
RESOLUTION (tcu.ini), 30
S
Screen resolution, 30
Select language (MUI), 50
Service Desktop
Background, 54
install, 78
Service switch, 125
Service system for PCU, 105
Shutdown, 124
SIMATIC STEP 7
Installing, 82
Software
Components, 6
install, 77
SSD
Replacing, 120
Starting OEM programs, 60
System boot, 123
T
Troubleshooting
Restore failure, 96, 101
U
USB FlashDrive, 105
User
Change the name, 22
Default, 11
Delete, 22
Inheritance, 19
User group, 11
User type, 11
V
Version software components, 6
VNC scanner, 128
W
Windows language (MUI), 50
PCU-Basesoftware (IM8)
138 Commissioning Manual, 02/2014, 6FC5397-1DP40-4BA0
Delivery condition 1
First commissioning of the
PCU 50.5 2
First commissioning of
SINUMERIK SIMATIC IPC627D or 3
IPC427D
Valid for:
Software:
SINUMERIK PCU-Basesoftware 50.5W7/IPC V11
10/2015
6FC5397-1DP40-5BA3
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Delivery condition.........................................................................................................................................7
1.1 PCU Base Software Windows 7...............................................................................................7
1.1.1 Overview..................................................................................................................................7
1.1.2 Supplied software.....................................................................................................................8
1.2 Hardware configuration of PCU 50.5.......................................................................................9
1.2.1 Network settings.......................................................................................................................9
1.2.2 Partitioning of the SSD.............................................................................................................9
1.3 Hardware configuration of IPC627D and IPC427D................................................................11
1.3.1 Network settings.....................................................................................................................11
1.3.2 Partitioning of the SSD...........................................................................................................11
1.4 Directory structure and file conventions.................................................................................13
2 First commissioning of the PCU 50.5.........................................................................................................15
2.1 Overview................................................................................................................................15
2.2 Backing up and restoring the delivery condition.....................................................................18
2.3 Install the PCU Base Software attended................................................................................19
2.4 Unattended installation of the PCU Base Software................................................................20
2.4.1 Configuring an answer file......................................................................................................20
2.4.2 Installing the PCU Base Software attended...........................................................................23
3 First commissioning of SIMATIC IPC627D or IPC427D.............................................................................25
3.1 Overview................................................................................................................................25
3.2 Installing the PCU-Basesoftware...........................................................................................26
4 Configuration of the system........................................................................................................................27
4.1 Overview................................................................................................................................27
4.2 Managing user accounts........................................................................................................28
4.3 Changing the name of the PC system...................................................................................29
4.4 Setting the IP address and domain........................................................................................30
4.5 Configuring USB interfaces....................................................................................................31
4.6 Configuring the keyboard layout............................................................................................32
4.7 Setting up an external screen................................................................................................33
4.8 Setting the screen resolution..................................................................................................34
4.9 Set the resolution in the tcu.ini...............................................................................................35
4.10 Setting the color depth in the tcu.ini file.................................................................................39
4.11 Activating/deactivating the multitouch operation of TCUs......................................................40
4.12 Calibrating the touch operation of a screen...........................................................................41
4.13 Configuring the SITOP UPS module for use with the PCU Base Software...........................42
4.13.1 Overview of SITOP UPS........................................................................................................42
4.13.2 SITOP modules for the PCU 50.5..........................................................................................43
4.13.3 Configuring SITOP software for PCU Base Software............................................................43
4.13.4 Parameterizing a delay time for quitting the HMI software.....................................................46
4.13.5 Hardware configuration of the SITOP UPS module...............................................................48
4.14 Configuration of the Service Center.......................................................................................51
4.14.1 Overview................................................................................................................................51
4.14.2 Configuration of the network adapter.....................................................................................52
4.14.3 Configuration of the host........................................................................................................53
4.15 Adapting the firewall settings.................................................................................................55
4.15.1 Overview................................................................................................................................55
4.15.2 Factory setting of the Windows Firewall on the Siemens PC system....................................56
4.15.3 General information on the operating principle of the Windows Firewall...............................57
4.15.4 General information on the settings recommended for Windows..........................................58
4.15.5 Configuration by means of a prompt or script/batch file.........................................................58
4.15.6 Enabling SNMP communication.............................................................................................59
4.15.7 Activate the remote access to the PC system........................................................................61
4.15.7.1 Overview................................................................................................................................61
4.15.7.2 Via the Control Panel.............................................................................................................61
4.15.7.3 By prompt, script or batch file.................................................................................................62
4.15.8 Activation/deactivation of the file and printer release.............................................................64
4.15.8.1 Overview................................................................................................................................64
4.15.8.2 General information................................................................................................................65
4.15.8.3 General activation for all network profiles..............................................................................66
4.15.8.4 Activation for a specific network profile..................................................................................69
4.15.8.5 Activation for a specific connection........................................................................................74
4.15.9 Activation of the ping execution (ICMP).................................................................................76
4.15.9.1 Via the Control Panel.............................................................................................................76
4.15.9.2 By prompt, script or batch file.................................................................................................77
4.15.10 Saving and restoring firewall settings.....................................................................................79
4.15.10.1 Overview................................................................................................................................79
4.15.10.2 Backup of firewall settings......................................................................................................79
4.15.10.3 Restoring of firewall settings..................................................................................................81
5 Installing and configuring updates and automation software......................................................................83
5.1 Overview................................................................................................................................83
5.2 Patch management and security updates..............................................................................84
5.3 Setting up SINUMERIK Operate for autologon mode............................................................85
5.4 Modifying the user account for autologon mode....................................................................87
5.5 Configuring a key filter for HMI software................................................................................89
5.6 Installing STEP 7....................................................................................................................93
5.7 Linking the HMI software with STEP 7...................................................................................94
5.8 PCU Installer..........................................................................................................................95
5.8.1 Overview................................................................................................................................95
5.8.2 Activating the PCU Installer...................................................................................................95
5.8.2.1 Overview................................................................................................................................95
1.1.1 Overview
The PCU-Basesoftware 50.5W7/IPC provides the basis for operating SINUMERIK software
(e.g. SINUMERIK Operate) on your SIEMENS PC system:
You can find an example sequence for commissioning and configuration under Overview
(Page 25).
You can find all of the information on the hardware in the corresponding documentation:
SIMATIC IPC627D operating instructions or SIMATIC IPC427D operating instructions.
Note
Do not switch off SIEMENS PC systems with Windows 7 on the hardware!
Loss of data may result on Windows-based systems if the system is not shut down properly
before it is disconnected from the power source. For technical reasons, data is still being written
to the SSD shortly after shutdown.
To avoid loss of data, use a SITOP UPS module.
See Configuring the SITOP UPS module for use with the PCU Base Software (Page 42).
Overview
The SINUMERIK PCU-Basesoftware contains the following software and tools:
Software Function
Microsoft Windows 7 Service Desktop
Microsoft Windows PE Service Center
Symantec Ghost Creating and restoring disk images
SIEMENS PCU Installer Installing software and updates
VNC Viewer Remote access to other devices from the PCU
PuTTy Remote access to other devices from the PCU
PuTTy Key Generator Generating an SSH key pair
Various configuration templates and scripts in the directory: Templates for simplifying configuration
C:\ProgramData\Siemens\MotionControl\SIEMENS
Note
Acknowledgements
● This product includes cryptographic software written by Eric Young ([email protected])
● This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit. (http://www.openssl.org/)
3&8
; ;
Further information
● Manual SINUMERIK 840D sl Operator Components and Networking
● Setting the IP address and domain (Page 30)
● Adapting the firewall settings (Page 55)
● Remote access (Page 148)
● Network settings in the Service Center (Page 111)
Further information
● SIMATIC IPC627 operating instructions
● SIMATIC IPC427 operating instructions
● Setting the IP address and domain (Page 30)
● Adapting the firewall settings (Page 55)
● Remote access (Page 148)
● Network settings in the Service Center (Page 111)
Note
Do not modify files in the template directory siemens!
The siemens directory contains only files with the factory settings that can be copied and
used as templates.
Never overwrite these files. Instead copy them into another directory (see Section Your
settings).
Your settings
Several directories are available into which you can copy and adapt configuration files in order
to make your own settings. In decreasing order of priority, these are:
● C:\ProgramData\Siemens\MotionControl\user\
● C:\ProgramData\Siemens\MotionControl\oem\
● C:\ProgramData\Siemens\MotionControl\addon\
The settings in a configuration file in a directory with higher priority always replace those from
one of lower priority. Template directory siemens has the lowest priority.
To define your own settings, therefore, copy a setting from the relevant template file into a
directory with higher priority, e.g. below directory user.
Note
Do not switch off the PCU 50.5 Windows 7 hardware!
Loss of data may result on Windows-based systems if the system is not shut down properly
before it is disconnected from the power source. For technical reasons, data is still being written
to the SSD shortly after shutdown.
To avoid loss of data, use a SITOP UPS module.
See Configuring the SITOP UPS module for use with the PCU Base Software (Page 42).
Example workflow
6HWXS3&8
%DFNXSGHOLYHU\
VWDWH
+HDGOHVV
1R
PRGH
LQWHQGHG"
<HV
&RQILJXUH &RQQHFWVFUHHQ
UHVSRQVHILOH
,QVHUW86%IODVKGULYH
ZLWKUHVSRQVHILOH 1R
$WWHQGHGLQVWDOODWLRQ
SRVVLEOH"
<HV
6ZLWFKRQ3&8 6ZLWFKRQ3&8
&RQQHFW3*3& ,QVWDOO:LQGRZV
DWWHQGHG
– Insert USB flash drive with ● Configure a response file and complete installation and user settings unattended
response file (Page 20).
● Attended installation possible? ● Connect screen (Page 33) and complete installation attended (Page 19), at the same
time set up users.
– Connect screen
– Install Windows 7 attended
4 Switch on PCU Do not switch on the PCU without the response file (Page 20) if you want the installation
to be performed unattended.
5 Connect PG/PC To be able to access a directory of a PG/PC in the network, for example, connect the PG/
PC in the network (Page 127).
&RQILJXUHQHWZRUN
VHWWLQJVRQ3*3&
6HWXSIXUWKHUXVHU
DFFRXQWV
,QVWDOOVRIWZDUHDQG
XSGDWHV
&RQILJXUHWKHV\VWHP
&UHDWHDGLVNLPDJH
EDFNXS
)LUVWFRPPLVVLRQLQJ
FRPSOHWHG
Requirement
The first commissioning of the PCU 50.5 (with "unattend.xml" response file or attended) has
not been performed yet.
Procedure
To back up the delivery condition of the PCU base software, proceed as follows:
1. Start the Service Center directly after switching on the PCU 50.5 the first time, e.g. via the
Windows boot menu.
Starting the Service Center (Page 108)
2. Back up the entire C: partition as disk image at another location, e.g. at D:
\DeliveryState_PCU-Basesoftware\
See also: Create a disk image of a partition (Page 118)
Result
The delivery condition is stored as disk image at the selected location. If required, you can
move this disk image to another location later.
First create a bootable USB flash drive (Page 126) with which you can restore this disk
image (Page 120).
After you have restored the delivery condition of a PCU 50.5 with a disk image, the first
commissioning starts at the initial startup with response file or attended.
Further information
● Backing up and restoring data (Page 107)
● First commissioning of the PCU 50.5 (Page 15)
Precondition
You can connect an operator panel front or screen and keyboard directly to the PCU 50.5.
Procedure
To perform attended installation of the PCU Base Software, proceed as follows:
1. Switch on the PCU 50.5.
The installation wizard guides you through the necessary steps.
2. During installation, create a Windows administrator account. You can create additional user
accounts in the Control Panel later. See also: Managing user accounts (Page 28).
3. Complete installation.
Result
Installation of the PCU Base Software with Windows 7 is performed. After attended installation,
you must activate the PCU Installer manually (Page 95).
See also
Microsoft TechNet - Methods for performing Windows setup (http://technet.microsoft.com/en-
us/library/dd744269.aspx)
Overview
The PCU-Basesoftware, Windows 7, is pre-installed on your PCU 50.5, but for security
reasons, final installation and the setting up of user accounts must be performed during initial
startup.
Obligatory settings
You preliminarily define the settings that you would normally have to make as user entries
during installation in unattend.xml. You must enter at least the following information:
● Name of the administrator account
● Password of the administrator account
● Password hint
● Confirmation of the EULA
OOBE/
NetworkLocation
OOBE/
HideEULAPage
unattend/ Create the administrator account (obliga‐
<LocalAccount wcm:action="add">
settings/ tory) <Name>auduser</Name>
Enter a user name in the Name element, <DisplayName>auduser</DisplayName>
component/ <Description>First admin account</
and a secure password in the Password/
UserAccounts/ Description>
Value element.
LocalAccounts/ <Group>Administrators</Group>
Specify the administrator status in the <Password>
LocalAccount Group element. <Value>SUNRISE</Value>
The DisplayName and Description el‐ <PlainText>true</PlainText>
ements are optional. </Password>
</LocalAccount>
In order to create additional user accounts,
insert the complete LocalAccount sec‐
tion a second time and there, change the
values of Name, Password/Value and, if
required, Group.
unattend/ Activate PCU Installer (optional) <SynchronousCommand wcm:action="add">
settings/ In order that the PCU-Basesoftware com‐ <CommandLine>"C:\Program Files (x86)\Siemens
ponent PCU Installer searches for setup \MotionControl\Siemens\System\etc
component/ \write_ini_entry.exe" "C:\ProgramData\Siemens
files directly after logging on, add this com‐
FirstLogonCommands/ mand. \MotionControl\user\System\etc\PCUInst.ini"
SynchronousCommand processing_loginphase StartState activated ENH</
As result, a setting is made in the ini file of CommandLine>
the PCU Installer. <Description>Set PCU Installer to start at user
So that you can store setup files in the D: login</Description>
\Install default installation directory, <Order>1</Order>
you must release this for the administrator </SynchronousCommand>
account in the unattend.xml (see
above).
Optionally, you can configure additional settings such as additional user accounts or network
settings.
Further information
You will find information about all options for adapting unattend.xml on the Microsoft website.
● Microsoft TechNet - Methods for performing Windows setup (http://technet.microsoft.com/
en-us/library/dd744269.aspx)
● Microsoft TechNet - Unattended Windows Setup Reference (http://technet.microsoft.com/
en-us/library/ff699026.aspx)
Requirement
● The PCU is in the delivery condition and switched off.
● In BIOS, the startup of the USB interfaces is deactivated.
In the PCU50.5, it is deactivated via a factory setting.
● A USB flash drive is available (e.g. SIMATIC PC USB-FlashDrive).
The USB flash drive must not use encryption, or it must be deactivated.
● The "unattend.xml" response file has been adjusted to your settings and at least one
administrator account with password is defined.
See: Configuring an answer file (Page 20).
Procedure
Proceed as follows to start unattended installation:
1. Copy your adjusted "unattend.xml" response file directly into the root directory of the USB
flash drive.
2. Connect the USB flash drive to the PCU.
3. Switch on the PCU.
Result
The first startup is performed as an unattended installation, using the settings that you specified
in the response file.
Note
Do not switch off SIEMENS PC systems with Windows 7 on the hardware!
Loss of data may result on Windows-based systems if the system is not shut down properly
before it is disconnected from the power source. For technical reasons, data is still being written
to the SSD shortly after shutdown.
To avoid loss of data, use a SITOP UPS module.
See Configuring the SITOP UPS module for use with the PCU Base Software (Page 42).
Example workflow
No Step Description
.
1 Set up and commissioning Information on setting up and installing your SIEMENS PC system can be found in the corresponding
of the PC system (according hardware documentation:
to the operating instructions) ● SIMATIC IPC627D operating instructions
Precondition
● You can connect an operator panel front or screen and keyboard directly to the PC system.
● The commissioning of the PC system (IPC627D or IPC427D) is completed and an
administrator account is set up.
● The PC system is switched off.
● The partition C: of the PC system has a minimum size of 30 GB.
● The installation medium is available on the PC system.
Procedure
To install the PCU-Basesoftware on your PC system, proceed as follows:
1. Open Windows Explorer and switch to the installation medium of the PCU-Basesoftware.
2. Double-click the file "setup.exe".
3. Restart the PC system after you have installed the PCU-Basesoftware.
Result
The SINUMERIK PCU-Basesoftware has been installed. During this, the previously existing
settings on the SIEMENS PC system, e.g. user accounts, keyboard layout, date and time
settings, were imported. Set up additional user accounts (Page 28) if necessary and set the
keyboard layout to English (Page 32).
The PCU Installer is at first disabled after the installation. It must be enabled (Page 95) before
software can be automatically installed.
Overview
During initial commissioning, you must create a local Windows administrator account and
define a password.
You can set up and manage additional Windows user accounts in the Control Panel. To do
that, log on with administrator rights.
Note
Administrator account cannot be recovered
If you have forgotten the password of the administrator account there is no way of recovering
it!
However, after initial commissioning, you can create a file with which you can later assign a
new password. To do that, in the Control Panel under user accounts use the "Create a
password reset disc" command.
See also: Microsoft Windows support - creating a password reset disk (http://
windows.microsoft.com/en-US/windows7/Create-a-password-reset-disk)
Further information
You can adapt the network settings for backing up and restoring disk images in the
configuration of the Service Center (Page 51).
You will find information about network settings under Windows 7 in the Windows help.
● To call up the Windows help, click "Help and Support" in the Start menu.
● You will find help for Windows 7 in the Internet on the Microsoft website: Microsoft Windows
support (http://windows.microsoft.com/en-US/windows/windows-
help#windows=windows-7)
Procedure
To activate or deactivate the USB interfaces, enter the relevant command on the Service
Desktop in the "Run" dialog box or at the prompt:
Table 4-1 Disabling USB interfaces with the "sc_usb disable" command
Factory setting: The USB interfaces are enabled in the delivery condition.
Syntax: sc_usb disable [-minutes] [all] [HOSTS...]
Description: ● Without a time indication [-minutes], a permanent disable is set.
With time indication, the disable takes the time set in minutes.
● The disable may refer to all network nodes of the system network,
or a list of host names or IP addresses may be specified to which
the disable should apply.
Table 4-2 Activating USB interfaces with the "sc_usb enable" command
Factory setting: The USB interfaces are enabled in the delivery condition.
Syntax: sc_usb enable
Description: With "sc_usb enable" USB storage units on permanently disabled
USB interfaces or on certain host names or IP addresses are ena‐
bled again.
Further information
You can find general information about a prompt on the Microsoft website.
● Prompt: Frequently asked questions (windows.microsoft.com/en-us/windows/command-
prompt-faq)
Requirements
● The PC system is switched off.
● The external screen is connected to the DVI interface of the PC system (with an adapter,
if necessary).
Procedure
To use an external screen for the Service Desktop or service system, proceed as follows:
1. Let the PC system boot in the Service desktop.
2. Right-click on the Desktop, then select "Screen Resolution" from the shortcut menu.
3. In the "Screen Resolution" dialog box, select the screen and set the resolution:
– If you are using an LCD or LED screen, you should ideally set the native resolution of
your screen.
– If you are using an older CRT screen, you can select any resolution.
4. Click "OK" to confirm the settings.
Result
The external screen has been connected and can be used.
Overview
The system behavior during run-up for the screen resolution is set in the tcu.ini file in
Section [VNCServer].
You will find a template of the tcu.ini under C:\ProgramData\Siemens\Motion
Control\siemens\System\etc\
Do not overwrite this template, but rather create your own tcu.ini inside one of the user
directories (see Chapter Directory structure and file conventions (Page 13)).
Further information
● Chapter Directory structure and file conventions (Page 13).
● Operator Components Manual, Chapter "Networking"
Settings Meaning
SYSTEM The resolution is not specially set during run-up. i.e. the resolution last used
in the system is active, e.g. the resolution which had been set manually in
the Control Panel.
AUTO_OP_1 Default setting:
During run-up, the resolution is automatically set ("PCU panel" has priority)
in accordance with the following scenarios:
Example 1: There is a PCU panel (irrespective of whether there is a PCU monitor and
TCU panels):
[In active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU panel
(max. 1920x1080).
Example 2: There is no PCU panel, however there is a PCU monitor (irrespective of
whether there are any TCU panels):
[In active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is not specially set; i.e. the resolution last used in the system
is active, e.g. the resolution which had been set manually in the Control Panel.
(Different to AUTO_OP_2 !)
AUTO_OP_2 Like AUTO_OP_1, except:
Example 2: There is no PCU panel, however there is a PCU monitor (irre‐
spective of whether there are any TCU panels):
[In active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU monitor, reduced to
the next lowest SINUMERIK resolution. The SINUMERIK resolutions are
640x480, 800x600, 1024x768, 1280x1024, 800x480, 1280x800, 1366x768
and 1920x1080.
Example: In the case of a PCU monitor with a max. resolution of 2048x1152,
the SINUMERIK resolution setting is 1920x1080.
AUTO_MON_1 During run-up, the resolution is automatically set ("PCU monitor" has priority)
in accordance with the following scenarios:
Settings Meaning
Example 1: There is a PCU monitor (irrespective of whether there is a PCU panel and
TCU panels):
[In active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU monitor, reduced to
the next lowest SINUMERIK resolution. The SINUMERIK resolutions are
640x480, 800x600, 1024x768, 1280x1024, 800x480, 1280x800, 1366x768
and 1920x1080.
Example: In the case of a PCU monitor with a max. resolution of 2048x1152,
the SINUMERIK resolution setting is 1920x1080.
If there is a PCU panel, the display there is panned if the max. resolution of
the PCU panel is lower than the max. resolution of the PCU monitor.
Example 2: There is no PCU monitor, however there is a PCU panel (irrespective of
whether there are any TCU panels):
[In active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is not specially set; i.e. the resolution last used in the system
is active, e.g. the resolution which had been set manually in the Control Panel.
(Different to AUTO_MON_2 !)
Example 3: There is no PCU monitor and no PCU panel (headless operation):
A) In active TCU mode:
a) Dynamic resolution switching is enabled (resolution adaptation entry in
TCU.ini) and at least one TCU is already logged on:
The resolution is set to the resolution of the TCU which is currently active.
b) Dynamic resolution switching is enabled (resolution adaptation entry in
tcu.ini) and no TCU has logged on yet or dynamic resolution switching is
disabled:
The resolution is set to the max. resolution of the current PCU panel, i.e.
which logged on during the previous session.
Default setting: Default TCU resolution in accordance with the registry.
Notice: The first TCU panel to log on is activated. The focus handler then
automatically sets the resolution to this TCU panel's resolution (in the case
of dynamic resolution switching).
B) In inactive TCU mode:
The resolution is not specially set - i.e. the resolution used during the previous
session in the system is active, e.g. the resolution set manually in Control
Panel.
AUTO_MON_2 Like AUTO_MON_1, except:
Example 2: There is no PCU monitor, however there is a PCU panel (irre‐
spective of whether there are any TCU panels):
[In active TCU mode:
The following additional condition applies: PCU is activated (with dynamic
resolution switching enabled)]:
The resolution is set to the max. resolution of the PCU panel
(max. 1920x1080).
640x480 During run-up, the SINUMERIK resolution is set to 640x480.
Settings Meaning
800x600 During run-up, the SINUMERIK resolution is set to 800x600.
1024x768 During run-up, the SINUMERIK resolution is set to 1024x768.
1280x1024 During run-up, the SINUMERIK resolution is set to 1280x1024.
800x480 During run-up, the SINUMERIK resolution is set to 800x480.
1280x800 During run-up, the SINUMERIK resolution is set to 1280x800.
1366x768 During run-up, the SINUMERIK resolution is set to 1366x768.
1920x1080 During run-up, the SINUMERIK resolution is set to 1920x1080.
Requirement
● Hidden directories are not shown
● A copy of the tcu.ini configuration file is stored in the user directory: C:\ProgramData
\Siemens\MotionControl\user\System\etc\tcu.ini
● The tcu.ini configuration file in the user directory is not write-protected
See: Directory structure and file conventions (Page 13)
Procedure
To adapt the color depth of the PC system, proceed as follows:
1. Open the tcu.ini configuration file in the C:\ProgramData\Siemens\MotionControl
\user\System\etc\ directory.
2. Enter the required value in the [VNCServer] section (below the #COLOR DEPTH comment):
– ColorDepth=0
The color depth is not changed during run-up, but rather the color depth used last is
retained. In this way, you can adapt the color depth in the Windows settings.
– ColorDepth=1 (default value)
The color depth is set to 16-bit during run-up.
– ColorDepth=2
The color depth is set to 32-bit during run-up.
3. Save and close the file.
Requirement
● Hidden directories are not shown
● A copy of the tcu.ini configuration file is stored in the user directory: C:\ProgramData
\Siemens\MotionControl\user\System\etc\tcu.ini
● The tcu.ini configuration file in the user directory is not write-protected
See: Directory structure and file conventions (Page 13)
Procedure
Proceed as follows to configure multitouch operation:
1. Open the tcu.ini configuration file in the C:\ProgramData\Siemens\MotionControl
\user\System\etc\ directory.
2. Enter the desired value:
– TouchSupport=1 (default value)
Multitouch operation is centrally activated for all of the TCUs that support the
functionality.
– TouchSupport=0
Multitouch operation is centrally deactivated for all of the TCUs that support the
functionality.
3. Save and close the file.
Result
The setting has been changed and is active after a restart of the Siemens PC system.
Requirement
● The Service Desktop is active.
Procedure
To calibrate the touch functionality of a screen, proceed as follows:
1. In the Start menu, click "Start > All Programs > Touchware > UPDD".
The "TouchWare Properties" dialog box opens.
2. In the "Calibrate" tab, click on "Calibrate" and follow the instructions that appear on screen.
You can find additional information in the dialog via the "Help" button.
4.13 Configuring the SITOP UPS module for use with the PCU Base
Software
NOTICE
Ensure the readiness for operation of the SITOP power supply
In order to prevent data loss, the SITOP power supply must be ready for operation. Note the
following:
● The SITOP power supply may not be ready for operation immediately after being switched
on (a capacitor-buffered UPS500 requires 1-2 minutes make time, for example).
● The operating system and the SITOP software must have run up so that the SITOP
software can shut down the system correctly when a power failure occurs.
● The readiness for operation and the functional capability of the SITOP power supply must
be ensured (e.g. battery of capacitor charged).
● Please also note all the information on the readiness for operation in the documentation
of your SITOP device.
Further information
Information on the use of SITOP UPS modules in combination with the PCU base software
can also be found on the Internet:
● Service & Support Portal: SINUMERIK PCU 50.5: Use of an uninterruptible power supply
(http://support.automation.siemens.com/WW/view/en/90142681)
● Service & Support Portal: Typical values for an operator station with PCU 50.5 Windows 7
(http://support.automation.siemens.com/WW/view/en/76773241)
● SITOP Selection Tool (http://www.siemens.com/sitop-selection-tool) (Tool for the selection
of a SITOP UPS module)
Note
Information about the test environment for machine OEMs
The functionality has been tested in the standard configuration with the PCU base software.
When installing add-on or OEM software components, you must check the shutdown
procedure of the entire system and adapt the factory setting (180 seconds).
See: Parameterizing a delay time for quitting the HMI software (Page 46)
Further information
Information about available SITOP UPS modules is given in the catalog or in the Internet:
● Service & Support Portal: SINUMERIK PCU 50.5: Use of an uninterruptible power supply
(http://support.automation.siemens.com/WW/view/en/90142681)
● Service & Support Portal: Typical values for an operator station with PCU 50.5 Windows 7
(http://support.automation.siemens.com/WW/view/en/76773241)
● SITOP Selection Tool (http://www.siemens.com/sitop-selection-tool) (Tool for the selection
of a SITOP UPS module)
● Catalog KT 10.1 Power supply SITOP
● SIEMENS Industry Mall > 24 V DC Uninterruptible Power Supplies (https://
eb.automation.siemens.com/mall/en/US/Catalog/Products/7010117)
Requirement
● The SITOP UPS hardware is connected via the USB interface.
● The SITOP software of version 3.x.2.16 or later is installed in directory C:\Program
Files (x86)\SITOP\
● If you want to use SITOP software of version 3.2.1.16 or older, this must be installed as a
normal application, not as a service.
Note
Windows service of the SITOP software version 3.2.1.16 or older is not compatible with the
PCU base software
If you use SITOP software of version 3.2.1.16 or older as a Windows service with the PCU
base software, the correct shutdown procedure cannot be performed!
If you have installed the SITOP software of version 3.2.1.16 as a Windows service, you
must uninstall this and install it again as an application in order to be able to use it in
conjunction with the PCU base software.
As of version 3.2.1.17, the SITOP software can be used as service with the PCU base
software and is recommended.
● The SITOP software was configured during the installation so that it starts automatically
when Windows is run-up (factory setting).
● The Service Desktop is active.
Procedure
Proceed as follows to configure the SITOP software for use with the PCU base software:
1. Call the settings of the SITOP software, for example, by right-clicking the SITOP UPS icon
in the Windows information area and then selecting "Configuration".
The "SITOP DC UPS Configuration" dialog box opens.
2. In the "General" tab, select "UPS" in the drop-down list at "Serial interface".
3. Switch to the "Floating operation" tab and make the following settings:
– Deactivate the "Display monitoring window after" checkbox
Note
Deactivating the monitoring window
Display of the monitoring window can cause malfunctioning of the HMI software.
– Click directly in the text field at "Start application after" and specify the path of the
USVShutdown.bat:
C:\Program Files (x86)\Siemens\MotionControl\siemens\sinumerik
\hmi\base\USVShutdown.bat
Note
Do not use the "Browse" button
The dialog can crash if you use the "Browse" button to specify the path of the
USVShutdown.bat.
Instead, enter the path directly in the text field.
– After you have specified the path of the USVShutdown.bat, activate the "Start
application after" checkbox. Optionally, you can specify the wait time after which the
USVShutdown.bat is to be executed (e.g. 5 seconds).
If the HMI software cannot be shut down within 180 seconds (factory setting) due to an error,
HMI software shutdown is forced and Windows 7 is shut down.
If the HMI software of your OEM installation is not shut down within 180 seconds, you can
parameterize this wait time manually.
Note
Information about the test environment for machine OEMs
The "SITOP UPS" function has been tested in the standard configuration with the PCU base
software. When installing add-on or OEM software components, you must check the shutdown
procedure of the entire system and adapt the factory setting.
Requirement
● The SITOP UPS module is configured for use with the PCU base software.
See Configuring SITOP software for PCU Base Software (Page 43).
● The Service Desktop is active.
Procedure
Proceed as follows to change the delay time:
1. Call the settings of the SITOP software, for example, by right-clicking the SITOP UPS icon
in the information area and then selecting "Configuration".
2. In the "SITOP DC UPS Configuration" dialog box, enter the wait time in seconds as a
command line parameter in the "Floating operation" tab:
– Syntax: <Path>\USVShutdown.bat -<Time in seconds>
– Example: C:\Program Files (x86)\Siemens\MotionControl\siemens
\sinumerik\hmi\base\USVShutdown.bat -180
Buffering parameterization
The UPS module can be used to select whether buffering should be completed after a
predetermined period of time or not until the accumulator’s lowest discharge threshold (=
maximum buffer time) has been reached. Both buffering parameterizations result from this.
On - Off
1 +2V
Cut-in threshold
2 +1V
+22V fixed
3 +0.5V
4 +1V
5 +1V
End-of-charge voltage
6 +0.5V
+ 26.3V fixed
7 +0.2V
8 +0.2V
9 +0.1V
10 0.35A / 0.7A Charging current
On - Off
1 Set time/max. time
2 +320 s
3 +160s
Buffer time
4 +80s
5 +40s
6 +20s +5 s fixed
7 +10s
8 Disconnection
9 Battery operating state on/off
Legend:
Delivery condition setting
Setting for operation on the PCU
On - Off
1 +2V
Cut-in threshold
2 +1V
+22V fixed
3 +0.5V
4 +1V ∘
5 +1V ∘
End-of-charge voltage
6 +0.5V
+ 26.3V fixed
7 +0.2V
8 +0.2V
9 +0.1V
10 0.35A / 0.7A Charging current
On - Off
1 Set time/max. time
2 +320 s ∘
3 +160s ∘
Buffer time
4 +80s
+5 s fixed
5 +40s
6 +20s
7 +10s
8 Disconnection
9 Battery operating state on/off
Legend:
Delivery condition setting
Setting for operation on the PCU
4.14.1 Overview
You can permanently adapt the settings for the backup and restoration of disk images (Service
Center (Page 107) component) in the "Service Center Backup/Restore" dialog box:
● Configuration of the network adapter (Page 52)
● Configuration of the host (Page 53)
Adaptations that you make here are stored in the servicesystem.ini configuration file.
You can also adapt the settings directly in the associated configuration files:
● servicesystem.ini
● Additional settings: ghost.ini
You can also view the log files of the Service Center or restart the PC system in the Service
Center in the "Service Center Backup/Restore" dialog box.
To open the dialog box, click the ServiceCenter Backup-Restore icon on the Desktop.
Overview
You can make the following IP settings in the "Adapter Settings" dialog box:
Settings Purpose
Default Gateway Set the IP address of the standard gateway.
A standard gateway creates a standard route in the IP routing table for all destinations that are
not in the subnet.
Name Server Set the IP address of the name server.
A name server answers questions asked about a domain name zone using a DNS database.
Overview
You can make the following settings in the "Host Settings" dialog box:
4.15.1 Overview
From a PG/PC in the plant network, you can directly access resources on the Siemens PC
system. The same applies when accessing a PG/PC from the Siemens PC system in the plant
network or in the company network.
If you want to access the Siemens PC system via the company network instead or in addition,
you must adapt the firewall settings.
&RPSDQ\QHWZRUN 3ODQWQHWZRUN
3*3& 3&8
)LUHZDOO
Table 4-6 Factory settings for network adapter and Windows Firewall
See also
Patch management and security updates (Page 84)
Saving and restoring firewall settings (Page 79)
You can make the Windows Firewall settings both via the Control Panel and via the prompt or
script/batch files. The use of script/batch files is particularly recommended for series
commissioning. Alternatively, for series commissioning, you can make all of the Windows
Firewall settings on an individual PC system, save these settings, and apply them on other
devices (Page 79).
Firewall settings recommended by Windows are unsuitable for use in the plant network
In the Control Panel, under "Windows Firewall", there is a display indicating that the firewall
settings do not correspond to the settings recommended and automatically checked by
Windows. The corresponding sections are highlighted in red:
The settings automatically recommended by Windows are not suitable for use in the plant
network, however, and would limit the functioning of the system. The network security in the
plant network must therefore be ensured by other security precautions. In this regard, observe
the information on industrial security (Page 84).
Note
Do not use the firewall settings that are automatically recommended by Windows!
The command "Use recommended settings" overwrites the existing firewall settings, which are
required for operating the PCU-Basesoftware, and therefore this command must not be used.
Otherwise, the Windows Firewall will be activated in the plant network and communication of
internal services of the PCU-Basesoftware will be inhibited.
Basic procedure
You can enter these commands either directly into the prompt or save the command in a script
or batch file:
● Direct input of the command:
– Call the prompt as the administrator.
– You can enter the commands either directly or in succession.
● Calling the command via a script file (or batch file):
– Save the command in a text file.
– Call the prompt as the administrator.
– Specify the script file as follows:
netsh -f <File name of the script file>
Further information
● MSDN Library - Netsh (command-line program) (https://msdn.microsoft.com/en-us/library/
cc785383(v=ws.7).aspx)
Procedure
To permit incoming SNMP communication on the Siemens PC system, proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
4.15.7.1 Overview
Basically, it is possible to access the Siemens PC system both via the plant network and via
the company network via VNC:
● The remote access to the Siemens PC system from a PG/PC in the plant network is
activated via the factory setting.
See: Connection options in the system network (Page 127)
● If you want to access the Siemens PC system via the company network instead or in
addition, you must adapt the firewall settings.
)LUPHQQHW] $QODJHQQHW]
3*3& 3&8
91&9LHZHU 91&6HUYHU
3RUW
The inbound rule "vnc5900", which is deactivated in the factory settings state, is available
for this purpose in the expanded settings for the Windows Firewall. To activate the remote
access to the PC system in the company network, you can activate this rule either directly
in the Control Panel (Page 61), or in the prompt or by means of a script/batch file
(Page 62).
Further information
In addition to the firewall settings, you may have to adapt other settings to establish a remote
connection in the company network. You can find additional information on this in Chapter
Remote access (Page 148), especially under Remote access to the PCU for operation and
maintenance (Page 149).
Procedure
To activate remote access from the PG/PC in the company network to the Siemens PC system,
proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
3. Click on "Advanced settings" and confirm the call of the expanded settings with "Yes" if
necessary.
4. In the "Windows Firewall with Advanced Security" dialog, right-click under "Inbound Rules"
on the rule "vnc5900", then click on "Enable Rule".
Result
With the activation of the inbound rule "vnc5900", Port 5900 was activated in the company
network, which allows remote access from a PG/PC to the Siemens PC system in the company
network.
If you want to deactivate remote access in the company network, right-click on the rule
"vnc5900" and select "Disable Rule" in the shortcut menu.
Further information
You can find general information on remote access to the Siemens PC system (via VNC Viewer
or SSH client) in Chapter Remote access (Page 148).
Basic procedure
With a command according to the following scheme, you can activate remote access from the
PG/PC in the company network to the Siemens PC system.
To do this, call the prompt as the administrator and enter the command either completely or
successively.
Alternatively, you can save the command and the associated parameters in a script file
(Page 58).
Table 4-7 Description of the Netsh commands in the context of the advfirewall firewall
Example
Further information
Descriptions of the commands and of all of the associated parameters of Netsh within the
Advfirewall firewall context can be found on the Microsoft website:
● Microsoft TechNet - Netsh AdvFirewall Firewall Commands (https://technet.microsoft.com/
en-us/library/dd734783(v=ws.7).aspx#BKMK_3_set)
● Microsoft TechNet - Use of the command line tool Netsh AdvFirewall (https://
technet.microsoft.com/en-us/library/cc770887(v=ws.7).aspx)
4.15.8.1 Overview
From a PG/PC in the plant network, you can easily and directly access a directory on the
Siemens PC system.
If you want to access the PC system via the company network instead or in addition, you must
adapt the firewall settings.
&RPSDQ\QHWZRUN 3ODQWQHWZRUN
3*3& 3&8
:LQGRZV([SORUHU 'LUHFWRU\
)LOHDQG
SULQWHUUHOHDVH
Figure 4-5 Access to a released directory of the PCU 50.5 from a PG/PC in the company network
Overview
You can activate the file and printer release either for all of the network profiles, for a specific
network profile, or for a specific network connection:
● General activation for all network profiles (Page 66)
– Via the Control Panel (Page 66)
– By prompt or script file (Page 67)
● Activation for a specific network profile (Page 69)
– Via the Control Panel (Page 69)
– By prompt or script file (Page 71)
● Activation for a specific connection (Page 74)
– Via the Control Panel (Page 74)
– By prompt or script file (Page 75)
This can be seen in the corresponding Windows Firewall settings dialogs by means of a
partially activated checkbox (green or gray background).
Further information
● Microsoft Windows support - File and printer release: Frequently Asked Questions (http://
windows.microsoft.com/en-us/windows/file-printer-sharing-faq#1TC=windows-7)
Procedure
To activate the file and printer release on the Siemens PC system, proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
3. Click "Allow a program or feature through Windows Firewall".
5. Activate the corresponding checkbox for the corresponding entry "File and Printer Sharing"
for the desired network profiles.
6. Click "OK" to confirm the change.
Basic procedure
With a command according to the following scheme, you can allow the file and printer release
in the company network for all of the network profiles together. All of the firewall rules of the
group "File and Printer Sharing" are changed for all network profiles.
To do this, call the prompt as the administrator and enter the command either completely or
successively.
Alternatively, you can save the command and the associated parameters in a script file
(Page 58).
Table 4-8 Description of the Netsh commands in the context of the advfirewall firewall
Example
Activation of the firewall rule "File and printer release" for the "Public" profile.
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=yes
Further information
Descriptions of the commands and of all of the associated parameters of Netsh within the
Advfirewall firewall context can be found on the Microsoft website:
● Microsoft TechNet - Netsh AdvFirewall Firewall Commands (https://technet.microsoft.com/
en-us/library/dd734783(v=ws.7).aspx#BKMK_3_set)
Procedure
To activate the file and printer release from a PG/PC in the company network to PCU 50.5 for
a specific network profile, proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
3. Click on "Advanced settings" and confirm the call of the expanded settings with "Yes" if
necessary.
4. In the "Windows Firewall with Advanced Security" dialog, right-click on the rule "Inbound
Rules", then click on "New Rule..."
5. In the "New Inbound Rule Wizard" dialog, select the option button "Predefined", select in
the "File and Printer Sharing" drop-down list, and click on "Next".
6. Depending on the network profile (e.g. Public or Domain) for which the file and printer
release is to be activated, check the corresponding checkbox.
7. Click "Next".
8. Select the option button "Allow the connection" and click on "Finish".
Basic procedure
With a command according to the following scheme, you can switch off the blocking of the file
and printer release by the Windows Firewall for a special network profile.
To do this, call the prompt as the administrator and enter the command either completely or
successively.
Alternatively, you can save the command and the associated parameters in a script file
(Page 58).
Syntax for the activation of all firewall rules regarding file and printer release
netsh
advfirewall firewall
set rule name="File and Printer Sharing (NB-Session-In)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (NB-Session-Out)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (SMB-In)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (SMB-Out)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (NB-Name-In)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (NB-Name-Out)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (NB-Datagram-In)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (NB-Datagram-Out)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (Spooler Service - RPC)" new
enable=yes profile=<profile>
set rule name="File and Printer Sharing (Spooler Service - RPC-EPMAP)" new
enable=yes profile=<profile>
set rule name="File and Printer Sharing (Echo Request - ICMPv4-In)" new
enable=yes profile=<profile>
set rule name="File and Printer Sharing (Echo Request - ICMPv4-Out)" new
enable=yes profile=<profile>
set rule name="File and Printer Sharing (Echo Request - ICMPv6-In)" new
enable=yes profile=<profile>
set rule name="File and Printer Sharing (Echo Request - ICMPv6-Out)" new
enable=yes profile=<profile>
set rule name="File and Printer Sharing (LLMNR-UDP-In)" new enable=yes
profile=<profile>
set rule name="File and Printer Sharing (LLMNR-UDP-Out)" new enable=yes
profile=<profile>
Table 4-9 Description of the Netsh commands in the context of the advfirewall firewall
Example
Example for the activation of all firewall rules regarding file and printer release
netsh
advfirewall firewall
set rule name="File and Printer Sharing (NB-Session-In)" new enable=yes
profile=public
set rule name="File and Printer Sharing (NB-Session-Out)" new enable=yes
profile=public
set rule name="File and Printer Sharing (SMB-In)" new enable=yes
profile=public
set rule name="File and Printer Sharing (SMB-Out)" new enable=yes
profile=public
set rule name="File and Printer Sharing (NB-Name-In)" new enable=yes
profile=public
set rule name="File and Printer Sharing (NB-Name-Out)" new enable=yes
profile=public
set rule name="File and Printer Sharing (NB-Datagram-In)" new enable=yes
profile=public
set rule name="File and Printer Sharing (NB-Datagram-Out)" new enable=yes
profile=public
set rule name="File and Printer Sharing (Spooler Service - RPC)" new
enable=yes profile=public
set rule name="File and Printer Sharing (Spooler Service - RPC-EPMAP)" new
enable=yes profile=public
set rule name="File and Printer Sharing (Echo Request - ICMPv4-In)" new
enable=yes profile=public
set rule name="File and Printer Sharing (Echo Request - ICMPv4-Out)" new
enable=yes profile=public
set rule name="File and Printer Sharing (Echo Request - ICMPv6-In)" new
enable=yes profile=public
set rule name="File and Printer Sharing (Echo Request - ICMPv6-Out)" new
enable=yes profile=public
set rule name="File and Printer Sharing (LLMNR-UDP-In)" new enable=yes
profile=public
set rule name="File and Printer Sharing (LLMNR-UDP-Out)" new enable=yes
profile=public
Further information
Descriptions of the commands and of all of the associated parameters of Netsh within the
Advfirewall firewall context can be found on the Microsoft website:
● Microsoft TechNet - Netsh AdvFirewall Firewall Commands (https://technet.microsoft.com/
en-us/library/dd734783(v=ws.7).aspx#BKMK_3_set)
Procedure
To activate the file and printer release for a specific connection (e.g. company network),
proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Network and Sharing Center" in the search field and then click on "Network and
Sharing Center" in the search results.
3. Click on the desired connection, e.g. "Local Area Connection 2" (company network).
4. Click on "Properties" and confirm the call of the properties with "Yes" if applicable.
5. In the "Networking" tab, check the checkbox "File and Printer Sharing for Microsoft
Networks" and confirm the change with "OK".
Example: Activation of the file and printer release for "Local Area Connection 2" (company network)
nvspbind -e "Local Area Connection 2" ms_server
Note
Dependency for the file and printer release
If you activated the file and printer release in the company network, incoming ping requests
are already permitted because they are required for the file and printer release.
Procedure
To permit ICMP pings, which arrive at the company network interface (X1) of the Siemens PC
system, proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
3. Click on "Advanced settings" and confirm the call of the expanded settings with "Yes" if
necessary.
4. In the "Windows Firewall with Advanced Security" dialog, click on "Inbound Rules".
Figure 4-6 Rules for incoming ICMP pings, separate for each network profile
Basic procedure
With a command according to the following scheme, you can permit ICMP pings which arrive
at the company network interface (X1) of the Siemens PC system. Outgoing pings from the
Siemens PC system are already activated.
Note
Dependency for the file and printer release
If you activated the file and printer release in the company network, incoming ping requests
are already permitted because they are required for the file and printer release.
The name of the relevant firewall rule is "File and Printer Sharing (Echo Request - ICMPv4-
In)". To do this, call the prompt as the administrator and enter the command either completely
or successively.
Alternatively, you can save the command and the associated parameters in a script or batch
file (Page 58).
Table 4-10 Description of the Netsh commands in the context of the advfirewall firewall
Example
Further information
Descriptions of the commands and of all of the associated parameters of Netsh within the
Advfirewall firewall context can be found on the Microsoft website:
● Microsoft TechNet - Netsh AdvFirewall Firewall Commands (https://technet.microsoft.com/
en-us/library/dd734783(v=ws.7).aspx#BKMK_3_set)
4.15.10.1 Overview
Overview
You can save all of the Windows Firewall settings of the Siemens PC system as a policy file
with the file extension ".wfw". Policy files are saved in binary format and are Windows version-
dependent.
You have the following options for backing up or restoring the firewall settings:
● Backup of firewall settings (Page 79)
– Via the Control Panel (Page 79)
– By prompt, script or batch file (Page 80)
● Restoring of firewall settings (Page 81)
You can restore the firewall settings on the same Siemens PC system or import the same
policy file to different Siemens PC systems for the purpose of series commissioning.
– Via the Control Panel (Page 81)
– By prompt, script or batch file (Page 81)
Procedure
To back up the Windows Firewall settings of the Siemens PC, proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
3. Click on "Advanced settings" and confirm the call of the expanded settings with "Yes" if
necessary.
4. Right-click on the master object "Windows Firewall with Advanced Security on Local
Computer" and then click on "Export Policy...".
5. In the "Save As" dialog, select a save location and file name and confirm with "Save".
Basic procedure
With a command according to the following scheme, you can back up the Windows Firewall
settings in a policy file (.wfw).
To do this, call the prompt as the administrator and first define the save location of the policy
memory, then enter a file path for backing up the policy file.
Alternatively, you can save the commands and the associated parameters in a script or batch
file (Page 58).
Syntax of the Netsh commands for defining the policy memory and for exporting the policy file
netsh advfirewall set store local
export <File path and file name>.wfw
Table 4-11 Description of the Netsh commands for defining the policy memory and for exporting the
policy file
Example
Example of the Netsh commands for defining the policy memory and for exporting the policy file
netsh advfirewall set store local
export D:\Backup\DefaultSettings.wfw
Further information
Descriptions of the commands and of all of the associated parameters of Netsh within the
Advfirewall context can be found on the Microsoft website:
● Microsoft TechNet: Netsh Commands for Windows Firewall with Advanced Security (https://
technet.microsoft.com/en-us/library/cc771920(v=ws.7).aspx)
Procedure
Note
Importing a policy file overwrites all existing firewall rules
When the firewall settings are restored, all of the existing firewall rules are overwritten. You
cannot undo the import of firewall rules via a policy file.
Therefore, back up (export) the existing firewall settings before you import a policy file.
To restore the Windows Firewall settings of the Siemens PC system, proceed as follows:
1. Click "Start > Control Panel".
2. Enter "Windows Firewall" in the search field and then click on "Windows Firewall" in the
search results.
3. Click on "Advanced settings" and confirm the call of the expanded settings with "Yes" if
necessary.
4. Right-click on the master object, then click "Windows Firewall with Advanced Security on
Local Computer", then click on "Import Policy..." and confirm the command with "Yes".
5. In the "Open" dialog, select the policy file and confirm with "Open".
Basic procedure
Note
Importing a policy file overwrites all existing firewall rules
When the firewall settings are restored, all of the existing firewall rules are overwritten. You
cannot undo the import of firewall rules via a policy file.
Therefore, back up (export) the existing firewall settings before you import a policy file.
With a command according to the following scheme, you can restore the Windows Firewall
settings from a policy file (.wfw).
To do this, call the prompt as the administrator and first define the save location of the policy
memory, then enter a file path for backing up the policy file.
Alternatively, you can save the commands and the associated parameters in a script or batch
file (Page 58).
Syntax of the Netsh commands for defining the policy memory and for importing the policy file
netsh advfirewall set store local
import <File path and file name>.wfw
Table 4-12 Description of the Netsh commands for defining the policy memory and for importing the
policy file
Example of the Netsh commands for defining the policy memory and for importing the policy file
netsh advfirewall set store local
import D:\Backup\DefaultSettings.wfw
Further information
Descriptions of the commands and of all of the associated parameters of Netsh within the
Advfirewall context can be found on the Microsoft website:
● Microsoft TechNet: Netsh Commands for Windows Firewall with Advanced Security (https://
technet.microsoft.com/en-us/library/cc771920(v=ws.7).aspx)
Overview
Microsoft regularly eliminates security holes in Windows and makes these corrections available
on its "Windows Update" website.
As a solution for managing and making Windows updates available in a network, Microsoft
offers the component Windows Server Update Services (WSUS).
Microsoft TechNet - Windows Server Update Services (http://technet.microsoft.com/en-us/
wsus/default.aspx)
Industrial security
You will find information about network security for an automation system and a comprehensive
protection concept under Industrial Security on the SIEMENS website:
SIEMENS Industrial Security (http://www.industry.siemens.com/topics/global/en/industrial-
security/)
SINUMERIK-specific information about Industrial Security can also be found in the following
documents:
SINUMERIK/SIMOTION/SINAMICS Configuration Manual Industrial Security (https://
support.industry.siemens.com/cs/document/108862708?lc=en-WW)
Generally, it is recommended that you check the compatibility of updates in a dedicated project
test environment before installing it in a productive environment.
Requirement
● A Windows user account without administrator rights is set up.
● SINUMERIK Operate is not installed.
● You are logged on as an administrator or you know the password of the administrator
account.
● The keyboard layout of the system is set to English.
See: Configuring the keyboard layout (Page 32)
Procedure
To set up autologon mode, proceed as follows:
1. Start installation of SINUMERIK Operate and, in the installation wizard, proceed to step
"Autologon".
Result
SINUMERIK Operate is installed and Autologon mode of the PC system is set up. During this
process the password of the autologon user account is stored encrypted in Windows, and
SINUMERIK Operate is linked with the autostart folder "Startup".
Autologon mode is active at the next startup. The autologon user account is automatically
logged on and SINUMERIK Operate is started.
Requirement
SINUMERIK Operate is installed and autologon mode is set up.
The Service Desktop is active.
Procedure
To change the user account that is used for automatic startup in autologon mode, proceed as
follows:
1. To open the "User Accounts" dialog box, proceed in one of the following ways:
– On the Desktop, double-click the "Netplwiz" icon.
– In the search field of the Start menu, enter netplwiz and confirm the entry.
– At the prompt, enter control userpasswords2.
The "User Accounts" dialog box opens.
Figure 5-2 "User Accounts" dialog box in Windows 7: Please note that the deactivated checkbox
refers to the selected user account.
2. Activate the "Users must enter a user name and password to use this computer" checkbox.
3. In the "Users for this computer" list, select the user account to be used for autologon mode.
4. Deactivate the "Users must enter a user name and password to use this computer"
checkbox.
You may be prompted to enter a password.
5. Confirm these settings in the "User Accounts" dialog box with "OK".
6. In the Autostart folder of the autologon mode user account, create a link to SINUMERIK
Operate.
Requirement
● The Windows 7 Service Desktop is active
● Hidden directories are shown
See also: Directory structure and file conventions (Page 13).
Procedure
To configure the key filter, proceed as follows:
1. Switch to the template directory: C:\ProgramData\Siemens\MotionControl
\siemens\System\etc\
The settings can be viewed in the template pcuhwsvc.ini.
2. Save a copy of the template pcuhwsvc.ini to one of the user directories:
– C:\ProgramData\Siemens\MotionControl\user\System\etc\
– C:\ProgramData\Siemens\MotionControl\oem\System\etc\
– C:\ProgramData\Siemens\MotionControl\addon\System\etc\
3. In the new file (e.g. ...\oem\System\etc\pcuhwsvc.ini), delete all data except for
the section name [KEYB_FILTER] and the keys that are to differ from the template.
All data and keys that do not occur in your file are automatically taken over from the template
in the siemens directory.
See also: Directory structure and file conventions (Page 13).
4. Save your file.
Example: Activating the key filter, but allowing use of the NUM-lock key.
This example activates the key filter (KeySequencesEnable = 1) and filters all possible
keyboard entries except the NUM-lock key.
Section [KEYB_FILTER]
Key SeqActive_x
Value 0 = specific keyboard entry activated
1 = specific keyboard entry will be filtered and is deactivated
Factory setting 1
[APPLICATION]
# ---------------------------------------
# STARTUP APPLICATION DIAGNOSTIC SECTION
# ---------------------------------------
[KEYB_FILTER]
# -------------------------------------------
# SIEMENS KEYBOARD-FILTER DRIVER SECTION
# -------------------------------------------
KeySequencesEnable = 0
SeqActive_0= 1
SeqActive_1= 1
SeqActive_2= 1
SeqActive_3= 1
SeqActive_4= 1
SeqActive_5= 1
SeqActive_6= 1
SeqActive_7= 1
SeqActive_8= 1
SeqActive_9= 1
SeqActive_11= 1
SeqActive_12= 1
SeqActive_13= 1
SeqActive_14= 1
SeqActive_15= 1
SeqActive_16= 1
SeqActive_17= 1
SeqActive_18= 1
SeqActive_19= 1
SeqActive_20= 1
Requirement
● The Service Desktop is active
● The STEP 7 product DVD is available on the PC system, e.g. via an external DVD drive or
network.
Procedure
1. To start the installation assistant of STEP 7, on the product DVD in directory "CD_1", double-
click setup.exe
2. Confirm the preselected directory under C:\Program Files (x86)\Siemens
\Step7\ as the installation directory.
3. In step "Transfer license keys", select "No, transfer license keys later".
Note
Licensing of STEP 7 with SINUMERIK Add-on
The licensing for STEP 7 is performed during installation of the SINUMERIK Add-on.
4. After you have installed STEP 7, restart the PC system and switch to the Service Desktop.
5. To start the installation wizard of the SINUMERIK Add-on, double-click setup.exe on the
product DVD in directory "Sinumerik_Add_On".
The installation wizard guides you through the following steps.
6. After you have installed the SINUMERIK Add-on, restart the PC system.
Result
STEP 7 has been installed with SINUMERIK Add-on.
The software has been registered in the Control Panel under the following designations:
● STEP 7 V5.5
● SINUMERIK Add-on for STEP7 V5.5
Requirement
● STEP 7 V5.5 SP3 or higher is installed
● The SINUMERIK Add-on for STEP 7 V5.5 or higher is installed
● An HMI software version is installed (SINUMERIK Operate or HMI Pro sl)
● The Service Desktop is active
Procedure
To add a softkey to the menu of the HMI software for starting STEP 7, proceed as follows:
1. Double-click the "STEP7-Authorizing" desktop icon.
Result
A softkey for starting STEP 7 has been added to the HMI software. This softkey requires access
level 3.
In C:\Program Files (x86)\Siemens\MotionControl\compat\add_on
\oemframe.ini, the following settings have been made for this purpose:
[s7tgtopx]
; with HMI-Advanced: eliminate minimize- / maximize-buttons of the
STEP7-window
WindowStyle_Off=196608
; with HMI-Advanced: switch to previous task when STEP7 is terminated
nSwitchToTaskAfterTermination= -2
Note
Adjustments for OEM configurations
The entries in oemframe.ini can be modified for OEM configurations.
For more information about templates for parameterizing the system, see Section Directory
structure and file conventions (Page 13).
5.8.1 Overview
The PCU Installer assists you with the installation of setup packages on PC systems:
● The PCU Installer checks definable setup directories on the PC system, on removable
disks, or in the network.
These setup directories must not be write-protected.
● If setup packages exist, they are automatically installed one after the other. The order in
which these packages are installed can be parameterized (Page 99).
● On the top right of the screen, a status display is displayed while the PCU Installer carries
out such activities.
For further information on the activities of the PCU Installer, see Chapter Procedure example
of an installation with the PCU Installer (Page 104).
5.8.2.1 Overview
In the delivery condition of the PCU base software, the PCU Installer is deactivated.
Requirement
● The PCU Installer is deactivated
● The Service Desktop is active
● The PCU Installer has not been configured yet and there is no adapted PCUInst.ini
configuration file
Procedure
To activate the PCU Installer by copying a preconfigured template, proceed as follows:
1. Copy the following file to the clipboard: D:\etc\Template_PCUInst.ini
2. Paste the file into the following directory: C:\ProgramData\Siemens\MotionControl
\user\system\etc
3. Rename the copied file to PCUInst.ini
Result
The PCU Installer has been activated and checks the setup directories during startup of the
PC system, but not during system operation.
The copied configuration file only differs from the default configuration file by the following
value:
[processing_loginphase]
StartState=activated
The settings of the copied configuration file are used because they are in a directory with higher
priority than the default configuration file.
See: Directory structure and file conventions (Page 13)
To also use the PCU Installer during system operation, you must make an additional setting
in the copied configuration file (Page 99):
[processing_systemphase]
StartState=activated
Note
Troubleshooting for incorrect installation routines
If completion of an installation requires a restart, but the installation cannot be completed after
the restart, the Service Desktop is not started.
In this case, restart the PC system in protected mode to prevent the PCU Installer from starting.
(To start in protected mode, press F8 repeatedly during startup until a selection menu opens.)
Then reconfigure the PCU Installer or remove the setup packages.
Requirement
● The Service Desktop is active
● Hidden directories are not shown (at least C:\ProgramData\)
See also: Directories hidden in delivery condition (Page 13).
● A copy of the PCUInst.ini configuration file is stored in the user directory: C:
\ProgramData\Siemens\MotionControl\user\System\etc\PCUInst.ini
● The PCUInst.ini configuration file in the user directory is not write-protected
Procedure
To partly or completely deactivate the installation of the setup files by means of the PCU
Installer, proceed as follows:
1. Open the PCUInst.ini configuration file in the C:\ProgramData\Siemens
\MotionControl\user\System\etc\PCUInst.ini directory.
2. Deactivate the start of the PCU Installer in the desired phase:
– To deactivate the PCU Installer during system operation, change the relevant key value
in the [processing_systemphase] section: StartState=stopped.
– To only deactivate the PCU Installer while a specific application is being executed (e.g.
SINUMERIK Operate), enter the file name of the relevant application in the
[noactivation] section, e.g. APP001=run_hmi.exe
(You can specify any number of applications, e.g.
APP002=Siemens.Automation.Portal.exe)
– To deactivate the PCU Installer during run-up, change the relevant key value in the
[processing_loginphase] section: StartState=stopped.
3. Save and close the file.
Further information
For information on all configuration options, see Reference to the PCUInst.ini configuration
file (Page 99).
Requirement
● The Service Desktop is active
● The PCU Installer has not been configured yet and there is no adapted PCUInst.ini
configuration file
Procedure
To copy and adapt the configuration file of the PCU Installer, proceed as follows:
1. Switch to the template directory: C:\ProgramData\Siemens\MotionControl
\siemens\System\etc\
The settings can be viewed in the template PCUInst.ini
2. Save a copy of the template PCUInst.ini to one of the user directories:
– C:\ProgramData\Siemens\MotionControl\user\System\etc\
– C:\ProgramData\Siemens\MotionControl\oem\System\etc\
– C:\ProgramData\Siemens\MotionControl\addon\System\etc\
3. Adapt the values of the keys. You will find information about the syntax and setting options
at Reference to the PCUInst.ini configuration file (Page 99) or in the comments of the
configuration file.
Note
The factory setting is taken if key pairs are missing
All key pairs that are not available in your file are taken automatically from the template in
the siemens directory.
Therefore, in the new file (e.g. ...\oem\System\etc\PCUInst.ini), delete all the data
except the section names and the keys that are to differ from the template.
See also: Directory structure and file conventions (Page 13), Reference to the PCUInst.ini
configuration file (Page 99)
Result
The configuration file has been copied to a user directory and can be adapted.
You will find further information on the setting options in the following chapters.
Note
Maximum length of the file path
The file path to a setup must not exceed 255 characters (including the file name).
Table 5-2 Setting options in the configuration file of the PCU Installer
Section Settings Description
[local_setupdirs] DIR001= Specifies the local setup directories on the PC system to be checked.
DIR002= The directories must not be write-protected.
... You can specify several directories, which are then checked in the specified order.
You define the order with a number after "DIR".
Subdirectories at the first level are also scanned.
[removable_ DIR001= Specifies the setup directories on removable disks to be checked.
setupdirs] DIR002= The directories must not be write-protected.
... You can specify several directories, which are then checked in the specified order.
You define the order with a number after "DIR".
Subdirectories at the first level are also scanned.
If you do not know the drive letters to be checked, use the <REMOVABLE_MEDIA>
drive variable, e.g.:
DIR001=<REMOVABLE_MEDIA>:\Install
The drive variable then represents all the removable disks that are known at the time
in Windows. You can also specify fixed drive letters without the directories being
checked twice.
The drive variable is only valid in the [removable_setupdirs] section.
[net_setupdirs] DIR001= Specifies the setup directories on network drives to be checked.
DIR002= The directories must not be write-protected.
... See also: Creating a shortcut to the network drive (Page 137)
You can specify several directories, which are then checked in the specified order.
You define the order with a number after "DIR".
Subdirectories at the first level are also scanned.
[setupdirs_ deleteTmpLocal Temporary directories are created during installation of a setup from a removable disk,
settings] SetupDirs= network drive or the default setup directory D:\Install
(See also: Procedure example of an installation with the PCU Installer (Page 104))
Here you can specify whether these temporary directories are to be deleted again
after installation.
Possible values: yes; no
keepDInstall You can specify that subdirectories of D:\Install with a particular prefix in the
SubdirsWithPrefix= directory name are not to be deleted after setup is completed.
[setupnames] NAME001= Specifies which files are setup packages and are to be included in the check of setup
NAME002= directories.
... You can specify entire file names with their file extensions or represent individual parts
of them with wildcard character *.
[setupexecution] checkSetupLogFile= Specifies whether a check is to be performed as to whether the file has already been
installed before the installation of a setup file.
The check is performed based on the computer name and the setup name of the setup-
specific log file.
Possible values: yes; no
copyToTmp You can specify whether setup files on removable disks are to be copied to a tempo‐
LocalSetupDir= rary, local directory before installation.
Setup files on network drives are always copied before installation.
Possible values: yes; no
[noactivation] APP001= Specifies which applications of the PCU Installer are inactive during operation.
APP002= This setting is required to prevent operation of the HMI software or another application
from being interrupted during execution of a setup.
5.8.6 Example configuration: Installation behavior as for PCU base software Windows
XP
If you want the automatic installation of setups to be configured in the same way as for the
PCU base software Windows XP, you can use the following configuration example in your
configuration file with higher priority.
[removable_setupdirs]
DIR001=E:\install
[processing_loginphase]
StartState=activated
scanRemovableDriveSetupDirs=yes
You can deactivate all other entries of a PCUInst.ini with lower priority by entering the
appropriate key in your configuration file, but leaving the value empty. For example, to
deactivate DIR002=C:\Setup in a configuration file of lower priority, enter DIR002= in your
file.
You can make any number of adaptations in your file. See: Reference to the PCUInst.ini
configuration file (Page 99)
Requirement
● The PCU Installer is activated
See: Activating the PCU Installer (Page 95)
● If you want to install multiple setup packages one after the other, you must have defined
multiple setup directories in the configuration file
● The setup directories to be used are empty and not write-protected
Procedure
To make the PCU Installer accessible to setup packages, proceed as follows:
1. Copy the setup packages to be installed into the setup directories. Copy each setup
package into a separate directory.
Note
Maximum length of the file path
The file path to a setup must not exceed 255 characters (including the file name).
Result
The installation of the setup packages is started.
After a setup has been completed or cancelled, a specific log file is stored in the associated
setup directory. The general log files of the PCU Installer are also supplemented in the log
directory.
Further information
● Log files (.log) (Page 105)
● Procedure example of an installation with the PCU Installer (Page 104)
Note
Troubleshooting for incorrect installation routines
If completion of an installation requires a restart, but the installation cannot be completed after
the restart, the Service Desktop is not started.
In this case, restart the PCU 50.5 in protected mode to prevent the PCU Installer from starting.
(To start in protected mode, press F8 repeatedly during startup until a selection menu opens.)
Then reconfigure the PCU Installer or remove the setup packages.
● The copied setup file is executed from the local temporary directory, e.g. D:
\Install39\Update.exe
● Log files are created after completion of the installation:
– The general log files are extended
– The setup-specific log file is created in the original setup directory F:\Setup and in the
local temporary directory D:\Install39
See: Log files (.log) (Page 105)
Archiving The setup directory in which the associated setup file was originally
located, and (if copied by the setup) the local temporary directory.
File name The log file is designated according to the following scheme:
<Name of the setup file>@<Computer name>.log, e.g. Update@MyP‐
CU50.log
If you activate the checkSetupLogFile= setting in the "PCUInst.ini" configuration file (Page 99),
then the setup-specific log file prevents the same setup being installed several times on the
same computer. The check is performed based on the computer name and the setup name.
In the delivery condition of the base software, this setting is deactivated. The setting should
remain deactivated for the series start-up of devices with the same name or for the repair of
an installation.
Archiving C:\ProgramData\Siemens\MotionControl\User\System
\Log\
File name PCU Installer client: PCUInstaller_C.log
5.9 Migration
Basic procedure
To transfer data from a PCU with Windows XP to a Siemens PC system with Windows 7, store
the data on a USB flash drive, for example, and then copy it to the PC system:
● For SINUMERIK Operate, use the functions for generating and reading in commissioning
archives.
● For STEP 7 V5.x, copy the generated STEP 7 project data onto the PC system.
Further information
● Information about how commissioning files work in SINUMERIK Operate can be found in
the SINUMERIK 840D sl SINUMERIK Operate Commissioning Manual (IM9), Chapter Data
backup.
● Information on STEP 7 V5.x can be found in the associated online help.
● Information about other SINUMERIK applications is provided in the relevant
documentation. You will find documentation on a large number of products in the SIEMENS
Service&Support portal:
Service&Support portal > CNC automation system SINUMERIK (http://
support.automation.siemens.com/WW/view/en/10805517/133300)
Overview
In the upper section of the Service Center main menu, you can select one of five tasks. Buttons
for additional functions are available in the lower section.
Note
Data backup and restore with CompactFlash cards
If there is a CompactFlash card in the slot of the PC system, you will not be able to back up
or restore data via the Service Center.
Instead, start the "ghost32.exe" program via the prompt of the Service Center.
Note
Temporarily storing network settings in the Service Center
Any network settings you make in this dialog box are immediately effective, but temporary.
To change network settings permanently, switch to the Service Desktop.
For further information, see Section Configuration of the Service Center (Page 51).
Overview
IP settings
You can make the following IP settings in the "Network Settings" dialog box:
Routing settings
You can make the following routing settings in the "Network Settings" dialog box:
See also
Network settings (Page 9)
Release directory of the PC/PC in the network (Page 134)
Creating a shortcut to the network drive (Page 137)
Configuring routing in the network (Page 129)
Procedure
To save the SSD as a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Starting the Service Center (Page 108)
2. In the main menu of the Service Center, click "Disk Backup".
The "Service Center - Disk Backup" dialog box opens.
4. Confirm your settings with "Backup" to start generation of the disk image.
Note
Restoring replaces all current files
When you restore the PC system from a disk image, all programs, settings and files are
completely replaced by the disk image. You cannot restore individual files or exclude individual
files from restoration.
Requirement
A disk image exists
See: Create a disk image of the SSD (Page 114)
Procedure
To restore a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Starting the Service Center (Page 108)
2. In the main menu of the Service Center, click "Disk Restore".
The "Disk Restore" dialog box opens.
4. To start the restore process and entirely replace the existing data on the SSD with the disk
image, confirm the settings with "Restore".
Result
The restore process is started.
Note
Troubleshooting if reading in of the disk image fails
If data transfer is interrupted during the restore process, the PC system will have no executable
system.
In this case, use a bootable USB flash drive with Service Center to read the disk image in
again.
Procedure
To save a partition of the SSD as a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Starting the Service Center (Page 108)
2. In the main menu of the Service Center, click "Partition Backup".
The "Service Center - Partition Backup" dialog box opens.
4. Confirm your settings with "Backup" to start generation of the disk image.
Note
Restoring replaces all current files
When you restore a partition from a disk image, all programs, settings, and files are completely
replaced on this partition by the disk image. You cannot restore individual files or exclude
individual files from restoration.
Requirement
A disk image of a partition exists
See: Starting the Service Center (Page 108)
Procedure
To restore a partition from a disk image, proceed as follows:
1. Start the Service Center, e.g. via the Windows boot menu.
See also: Create a disk image of a partition (Page 118)
2. In the main menu of the Service Center, click "Partition Restore".
The "Partition Restore" dialog box opens.
4. To start the restore process and entirely replace the existing data on the partition with the
disk image, confirm the settings with "Restore".
Result
The restore process is started.
Note
Troubleshooting if reading in of the disk image fails
If data transfer is interrupted during the restore process, the PC system will have no executable
system.
In this case, use a bootable USB flash drive with Service Center to read the disk image in
again.
Requirement
The network directory is shared with the relevant user accounts in the domain and on the PC
system.
See also: Release directory of the PC/PC in the network (Page 134)
Overview
The setting options in the "Connect a share" dialog box have the following meaning:
Table 6-4 Settings in the "Connect a Share" dialog box in the Service Center
Section Settings Purpose
Connection Local drive To select drive letters under which the network directories are to be accessible on the PC system.
Remote path Specify the device in the network and share name of the resource.
Syntax: \\Name of the server\share name of the network directory
Example: \\Backup_Server\PCU_Backup
Credentials User name Enter the user account under which the resource in the network can be accessed.
If you have shared the resource on the server for certain users only, you must enter one of these user accounts
here.
Password Enter the password of the user account.
Further information
You will find information about releasing directories in the network and network drives in the
following chapters:
● Release directory of the PC/PC in the network (Page 134)
● Creating a shortcut to the network drive (Page 137)
Procedure
To start Symantec Ghost directly, proceed as follows:
1. Call the prompt from the Service Center or the Service Desktop.
2. Enter "ghost.32.exe" and confirm the entry.
Further information
More information is available in the Internet on website Ghost.com (http://www.ghost.com).
Usage
You can generate a bootable Service Center (Emergency Boot System) based on Microsoft
Windows PE on a USB flash drive as preventive measure against a defect.
The Ghost image for the creation of the bootable USB flash drive is on the installed PCU base
software at: D:\Eboot\eboot.gho
Requirement
● The Windows 7 Service Desktop is active
● You have a USB flash drive (e.g. SIMATIC PC USB flash drive)
Procedure
To create a bootable USD flash drive, proceed as follows:
1. Connect the USB flash drive to a USB interface of the PC system.
2. Start Symantec Ghost, for example, by entering Ghost32.exe in the search bar in the
start menu.
3. In Symantec Ghost, select the "From Image" command from the "Local > Disk" menu.
4. Select D:\Eboot\eboot.gho as the source and the USB flash drive as the destination.
Result
The Emergency Boot System is installed on the USB flash drive and the data medium is
renamed to "EBOOT". The Service Center on the bootable USB flash drive can now be used.
6.12.1 Overview
System network
In the following applications, you will need, for example, a connection between the PC system
and a PG/PC in the system network:
● Save the disk image of the SSD to a PG/PC
● Restore the SSD of a PC system via the DVD drive of a PG/PC
● Start up the replacement SSD
● Install the software on the PC system via the DVD drive of a PG/PC
Company network
If you want to connect the service PG/PC via a company network (Local Area Connection 2;
interface X1), contact your network service center.
More information on the Windows Firewall settings in the company network can be found in
the section Adapting the firewall settings (Page 55).
Overview
The following figures show the typical connection options in the system network:
● Service PG/PC with (twisted) Ethernet cable direct to interface "X2" of the Siemens PC
system.
● Service PG/PC with (non-twisted) Ethernet cable via switch to interface "X2" of the Siemens
PC system.
Configuration with PG/PC direct to the Siemens PC system (e.g. PCU 50.5)
3*3&
3ODQWQHWZRUN
;
3&8
&RPSDQ\QHWZRUN ;
Configuration with PG/PC and switch direct to the Siemens PC system (e.g. PCU 50.5)
3ODQWQHWZRUN
7&8 3*3&
6ZLWFK
;
3&8
&RPSDQ\QHWZRUN
Note
If a PCU without its own OP/TP including TCU is switched off and then back on, and if this is
to be followed by the power up of the PCU of the service system (EBS), an external screen
and keyboard are needed to operate the PCU.
An external screen and keyboard are not needed if the TCUs are operating and the PCU is
not switched off with the EBS during booting.
Basic procedure
On the PG/PC with Windows 7:
● Connecting a PG/PC to a Siemens PC system according to one of the configurations shown
above.
● The network protocol used is: TCP/IP.
TCP/IP is already pre-configured on the Siemens PC system.
● Setting up IP addresses on the same subnetwork.
● Releasing a directory on the PG/PC for network access.
On the Siemens PC system in the Service Center (WinPE):
● On the PCU start the Service Center (WinPE).
● Establish a network connection to the shared directory of the PG/PC.
See: Functions of the Service Center (Page 109)
Further information
● Further information on the permissible network structures and network configurations can
be found in the SINUMERIK 840D sl Operator Components and Networking Manual.
Overview
If you have connected a PG/PC at interface X127 of the NCU, configure the network routing
to establish the connection between the PG/PC and the PCU.
7&8
6\VWHPQHWZRUN,QGXVWULDO(WKHUQHW
;
;
1&8 3&8
; ;
;
3*3&
&RPSDQ\QHWZRUN
Conditions
The following conditions must be met in order to use this function:
● The PG must be connected to interface X127 of an NCU in the system network.
● The NCU and PCU must be connected via the system network.
● On the NCU, the routing is activated in one of the following ways:
– In SINUMERIK Operate 4.5 SP2 or higher, the routing is configured in image "Settings
of the system network".
– In the configuration file basesys.ini, key EnableSysNetToIBNForwarding=1 is set.
● If you wish to access a network directory, it must be shared.
● The user account in question is known to the PG/PC.
● The Service Center is active.
Procedure
To configure the IP routing in the Service Center, proceed as follows:
1. In the main menu of the Service Center, click "Network".
2. In the "Network Settings" dialog box, click the "IP Routing" tab.
3. Configure the necessary routes. See also: Network settings in the Service Center
(Page 111)
Result
The routing has been configured and the PG/PC and Siemens PC system are connected via
the NCU.
Now, perform the desired steps, for example, a Restore a disk image of the SSD (Page 116).
Precondition
● The PG/PC is linked with the Siemens PC system in one of the following ways:
– The PG/PC is connected to the PC system with an Ethernet cable (either directly or via
a switch)
See: Connection options in the system network (Page 127)
– The PG/PC is networked with the PC system via an interface on the NCU and the routing
is configured.
See: Configuring routing in the network (Page 129)
● A current Microsoft Windows operating system is installed on the PG/PC
● The PG/PC is switched on
Procedure
To configure the network settings of the PG/PC for connecting a PC system in the system
network, proceed as follows:
1. Open the "network connections" window:
– To do this under Windows XP: in the "Start > Control Panel > Network and Internet
Connections" menu, choose "Network Connections."
– To do this under Windows 7: in the Control Panel in category "Network and Internet >
View network status and tasks," choose "Change adapter settings."
2. Right-click on the network adapter you want to configure, then choose "Properties" from
the shortcut menu.
This opens the "Properties of <connection>" dialog box.
– To change the IP address of the PG/PC, double-click "Internet Protocol Version 4 (TCP/
IPv4)", then configure the settings as follows:
Result
The network settings of the PG/PC are now configured for use with the Siemens PC system.
Requirement
● The PG/PC is switched on.
● There is sufficient space on the PG/PC for saving, for example, disk images from the PCU.
● The user accounts to which you want to grant share rights are known in the domain or on
the Siemens PC system.
Procedure
Proceed as follows to share a directory for use in the network:
1. On the PG/PC, in the Control Panel call up Computer Management.
2. Under "System > Shared Folders" select the file "Shares."
3. In the "Action" menu, click the "New File Share..." command.
The "Create A Shared Folder Wizard" opens.
4. Under step "Name, Description, and Settings," make a note of the Share path, which is a
combination of the computer name and the share name. You will have to specify this name
when you create a link to the network drive on the Siemens PC system.
Figure 6-14 Create A Shared Folder Wizard - Name, Description, and Settings
5. Under step "Shared Folder Authorizations," select the "Customize authorizations" radio
button, then click "Custom..."
Figure 6-17 "Select Users, Computers, Service Accounts, or Groups" dialog box
7. In section "Authorizations for <user name>," under column "Allow," click the "Change"
checkbox.
8. Confirm these settings in the "Customize PermiAuthorizations" dialog box with "OK."
9. In the next steps of the wizard, make all the settings you require and confirm the share with
"Finish".
Requirement
● The PG/PC is switched on.
● The Service Desktop is active.
● The folder on the PG/PC is shared for the relevant user accounts on the domain and on
the PC system.
Procedure
Proceed as follows to connect a shared directory as a network drive:
1. Start the Windows Explorer and click the "Map network drive" button.
2. Make the following settings in the "Map network drive" dialog box:
Settings Purpose
Drive To select drive letters under which the network directories are to be accessible
on the PC system.
Folder Specify the device in the network and share name of the resource.
Syntax: \\Name of the server\share name of the network
directory
Example: \\Backup_Server\PCU_Backup
Reconnect at logon Select this checkbox to automatically connect the network drive on booting.
Connect using dif‐ Select this checkbox if you have not shared the directory in the network with
ferent credentials the user for whom you would like to set up the network drive.
In the next dialog box "Enter Network Password," enter the log-on information
of a user with whom the network directory is shared.
See also
Microsoft Windows support (http://windows.microsoft.com/en-US/windows/windows-
help#windows=windows-7)
Note
Troubleshooting if reading in of the disk image fails
If data transfer is interrupted during the reading process, there will be no executable operating
system available on the Siemens PC system.
In this case, use a bootable USB flash drive with Service Center to read the disk image in
again.
See also
Network settings (Page 9)
Restore a disk image of the SSD (Page 116)
Intended use
The PCU hardware supports the diagnostics of important system components via an integrated
"safecard", which is designated as a Safecard-On-Motherboard (SOM).
Monitored Parameters
The following physical parameters of the PCU hardware are monitored:
● CPU temperature
● Housing temperature
● I/O chip temperature
● Speed of the two housing fans
● S.M.A.R.T - status of the hard disk
Logging faults
The PCU hardware monitor logs all hardware faults in the Windows event log so that the faults
can be output even without installing an HMI software.
The alarms are output in the log under "Control Panel" → "Administrative Tools" → "Event
Viewer".
See also
● Starting up the replacement SSD (Page 139)
● Operator Components and Networking Manual: Chapter, spare parts
● Description of the alarms: SINUMERIK 840D sl Diagnostics Manual
+ +
Figure 7-1 Diagnostics displays H1 and H2 of the PCU 50.5 with LEDs and 7-segment displays
Further information
Additional information on the diagnostics display, e.g. the meaning of the BIOS POST codes,
can be found in the Manual SINUMERIK 840D sl Operator Components and Networking.
Table 7-1 Status codes of the diagnostics display during the system power up
Table 7-3 Status codes of the diagnostics display during the shutdown process
Further information
You can find details on the hardware of the PCU 50.5 in the Manual SINUMERIK 840D sl
Operator Components and Networking.
Section [GLOBAL]
Key ModeSwitch=
Value 0 = Normal mode
3 = Desktop mode (startup in the welcome screen)
Other modes (Page 145) are not permitted in the software-side setting for SIMATIC IPC.
Factory setting 0
Requirement
● SINUMERIK Operate is installed and autologon mode is set up.
See Chapter Setting up SINUMERIK Operate for autologon mode (Page 85).
● The PCU is switched off.
Procedure
To switch to the desktop when the autostart/autologon mode is activated, proceed as follows:
1. Switch on the PC system and wait until the "SINUMERIK" welcome screen is displayed.
2. While the "SINUMERIK" welcome screen is being displayed, make one of the following
entries:
– Press the key 3 on your keyboard.
– Click or tip the copyright information.
The counter for starting SINUMERIK Operate is suspended and you can select one of three
options:
Result
The Service Desktop opens.
7.5.1 Overview
You can use a remote connection to access other devices via the network:
● Access to maintenance with prompt (SSH) via PuTTy.
● Access via VNC Viewer with all of the operating and servicing options, which are also
provided directly on the Siemens PC system.
See also
Setting up and using SSH (Page 151)
sc_show_net command
This command is executed in the prompt:
Procedure
Proceed as follows to show accessible nodes:
1. Select "MENU SELECT" to open the menu.
2. In the horizontal softkey menu, choose "Diagnostics > Bus TCP/IP."
3. In the vertical softkey menu, choose "TCP/IP > Diagnostics Network > Accessible nodes."
The "Accessible nodes" screen opens showing all nodes that use the SNMP or DCP
protocol.
Further information
You will find Information about showing accessible nodes in SINUMERIK Operate in the
SINUMERIK 840D sl SINUMERIK Operate (IM9) Commissioning Manual, Section Service and
diagnostics.
Note
Defining a secure password for the VNC server
To access the PCU 50.5 by remote access, you require a password. The factory setting of the
password in the VNC Server on the PCU 50.5 is "password". Modify this password during
commissioning in the settings of the VNC server to avoid security risks.
Further information
● Further information on the permissible network structures and network configurations can
be found in the Operator Components and Networking Manual.
Note
Do not change the factory settings!
To ensure that the VNC viewer works properly, the following options must not be changed.
Table 7-5 Connection settings in the start dialog of the VNC Viewer
Set up infrastructure on devices Supplied script ssh_key_log‐ C:\ProgramData\Siemens\Mo‐ Call up the script via the prompt. To do
in.bat tion Control\siemens\etc. this, enter user name and file name of
\ssh_key_login.bat the public key as the parameters.
Syntax:
ssh_key_login.bat <user
name> <public key>
Example:
ssh_key_login.bat username
publicKey.pub
Access devices via remote con‐ PuTTy C:\Program Files (x86)\PuTTy Online help in PuTTy
nection \putty.exe
See also
Remote access (Page 148)
Encryption via SSH protocol (Page 152)
Security
The security of SSH is ensured by a series of cryptographic algorithms for encryption and
authentication.
Authentication
The server identifies itself to the client with an RSA, DSA or ECDSA certificate, which enables
detection of manipulation in the network (no other server can identify itself as a known server).
The client can authenticate itself either by public key authentication with a private key whose
public key is stored on the server, or with a normal password. While in the latter case, user
interaction is always necessary (unless the password is stored unencrypted on the client
computer), public key authentication allows client computers to log on to SSH servers without
user interaction, without a password having to be stored in plain text on the client. However,
for added security the private SSH keys can also be protected with a password.
Subsystems
In the case of Secure Subsystem Execution, subsystems that were defined in an SSH server
installation can be executed remotely without knowing the precise path of the program
executed on the server. SFTP is the most common subsystem.
Further information
● Chapter Setting up and using SSH (Page 151).
● "NCU Operating System" Commissioning Manual (IM7).
● Description of PuTTy.
7 D
7-segment display, 142 DHCP, 9, 11
Diagnostics display, 142
Dialog box
A netplwiz, 87
ServiceCenter Backup/Restore, 51, 52, 53
Answer file, 20
Directory
Autologon, 20
C:\ProgramData, 13
Switch to Service Desktop, 146
D:\Install, 20
Autologon mode, 87
Disk image
AutoRepeat, 89
Restoring, 116, 120
Troubleshooting, 117, 122
DOS shell, (Prompt)
B
Backup time, 48
Batch file E
USVShutdown.bat, 43, 46
Emergency Boot System, 126, 145
Batch processing file, (Batch file)
BIOS
BIOS post code, 142
Factory setting, 145
F
Boot stick, 126 FirstLogonCommands, 20
C H
Color depth, 39 Hard disk
Command, (Command) Replacing, 139
control userpasswords2, 88 HMI software, 94
sc_show_net, 148
sc_usb disable, 31
sc_usb enable, 31 I
Command line, (Prompt)
Initialization files, (Configuration file)
Commissioning
Input area scheme, (Keyboard layout), (Keyboard
unattended, 20
layout)
USB flash drive, 20
Installation, (See Commissioning)
with identical settings, 20
Interface
Configuration file
Ethernet, 9, 11
Archive, 13
X1, 9, 11
basesys.ini, 130
X2, 9, 11
ghost.ini, 51
oemframe.ini, 94
pcuhwsvc.ini, 89, 145
PCUInst.ini, 95, 97, 98, 99
K
servicesystem.ini, 51, 52, 53 Key, (Repeat function)
tcu.ini, 34, 35, 39, 40, 149 Key filter, 89
Templates, 13 Key filter, 89
P T
Password, (Password) Troubleshooting
Administrator account, 20, 28 PCU Installer, 97, 104
Authentication for SSH encryption, 152 Restore failure, 117, 122
U
Uninterruptible power supply, 42
USB FlashDrive, 126
USB interface
Activating, 31
Disabling, 31
User account, (Setting up for autologon mode)
Setting up, 27, 28
Setting up for autologon mode, 85
User administration, 28
V
VNC Viewer, 149
X
XML
Response file, 20
unattend.xml, 20
XML file
unattend.xml, 20, 23