SoftwareGuide Blocks S7-1500 2018
SoftwareGuide Blocks S7-1500 2018
Powertrain
Software Guide
PLC Programming Guide
SINUMERIK Integrate
Run MyHMI /PRO (S7-1500)
2018 Edition
siemens.com/TRANSLINE
General information 1
Block overview 2
Program structure 3
Solutions for Powertrain
Connecting the control 4
TRANSLINE sl - Software Guide elements to the
controllers
PLC Programming Guide
SINUMERIK Integrate Relationship between 5
the axis selection
Run MyHMI /PRO screen and HMI PRO
(S7-1500)
Modes of Safe
Operations
6
Manual
PDA functions 8
Diagnostics in HMI
PRO
9
Valid for:
SIMATIC S7-1500
Using GRAPH blocks 11
Appendix, Change
directory
A
Edition 2018
Block index I
SINUMERIK® documentation
Printing history
Brief details of this edition and previous editions are listed below.
The status of each edition is shown by the code in the "Remarks" column.
© Siemens AG 2018. All Rights Reserved. We reserve the right to make technical changes.
Contents
1.3 Blocks that are absolutely necessary when using HMI PRO ....... 1-16
4.1 Communication levels with PROFINET and Industrial Ethernet ... 4-41
5 Relationship between the axis selection screen and HMI PRO . 5-57
8.2 Type preselection, workpiece overview and part counter ............ 8-121
8.2.1 Type preselection....................................................................... 8-123
8.2.2 Workpiece overview ................................................................... 8-124
8.2.3 Workpiece count ........................................................................ 8-129
10 Special features for HMI PRO with 1:N and virtual stations ..... 10-143
Figures
Fig. 7-7: Configuring setup screens in HMI PRO CS: Properties, left .................................................... 7-106
Fig. 7-8: Supply of the direct key screens (example for the 1st direct key left '-') ................................... 7-107
Fig. 7-9: Call sequence for direct key screens in the controller .............................................................. 7-109
Fig. 7-10: LTLP_DirectKey [FC511] ....................................................................................................... 7-110
Fig. 7-11: LTLP_DirectKey parameter ................................................................................................... 7-110
Fig. 7-12: LTLP_GetDirectKeyMoveNo [FC512] .................................................................................... 7-113
Fig. 7-13: LTLP_GetDirectKeyMoveNo parameter ................................................................................ 7-113
Fig. 8-1: Call sequence of PDA functions .............................................................................................. 8-115
Fig. 8-2: Interrelationship between LTLP_CycleTime and HMI PRO ..................................................... 8-116
Fig. 8-3: LTLP_CycleTime [FB523] ........................................................................................................ 8-117
Fig. 8-4: LTLP_CycleTime parameter .................................................................................................... 8-118
Fig. 8-5: Cycle time "START" and "STOP" with HOLD .......................................................................... 8-119
Fig. 8-6: Cycle time "START_STOP" with HOLD ................................................................................... 8-119
Fig. 8-7: Relationship between type preselection, workpiece overview and part counter ...................... 8-121
Fig. 8-8: Configuring more than 32 workpiece types .............................................................................. 8-122
Fig. 8-9: Interrelationship between the screen Workpiece count and block LTLP_WorkpieceCount ..... 8-129
Fig. 8-10: HMI PRO CS – workpiece overview, workpieces per station ................................................. 8-130
Fig. 8-11: LTLP_WorkpieceCount [FB522] ............................................................................................ 8-131
Fig. 8-12: LTLP_WorkpieceCount parameter ........................................................................................ 8-132
Fig. 8-13: Example of station index 2 ..................................................................................................... 8-133
Fig. 8-14: LTLP_ToolLifeTime [FB521] .................................................................................................. 8-137
Fig. 8-15: LTLP_ToolLifeTime parameter .............................................................................................. 8-137
Fig. 9-1: LTLP_SLDiagnosticCommand [FC599] ................................................................................... 9-141
Fig. 9-2: LTLP_SLDiagnosticCommand [FC599] ................................................................................... 9-141
Fig. 10-1: Example of a 1:N configuration with 4 SIMATIC PLCs……………………………………………...10-143
Fig. 10-2: Example of a configuration with 4 virtual stations ................................................................ 10-144
Fig. 10-3: Configuring 1:N controller connections for SIMATIC-PLCs S7-1500 ................................... 10-145
Fig. 10-4: Configuring virtual stations for SIMATIC PLCs S7-1500 ...................................................... 10-146
Fig. 10-5: Possible configurations of the controller texts in the function key menu .............................. 10-148
Fig. 10-6: Configuration and data variable using setup screen 1 as example ...................................... 10-149
Fig. 10-7: Configuration static and data variable using setup screen 1 as example ............................ 10-149
Fig. 10-8: Configuration and data from controller PLC1 using setup screen 1 as example.................. 10-150
Fig. 10-9: Softkey/function key number of a screen in the function key screen ................................... 10-155
Fig. 11-1: Properties of the GRAPH block: setting the version………………………………...…………….…11-157
Fig. 11-2: Integration of the LTLP_GraphManualExecutable as extension block ................................. 11-158
Fig. 11-3: Integration as multi-instance of a GRAPH block .................................................................. 11-158
Fig. 11-4: Integration as single-instance of a GRAPH block ................................................................ 11-159
Fig. 11-5: Example: Calling the GRAPH block as single instance........................................................ 11-159
Fig. 11-6: Instance name of the GRAPH block is cyclically read.......................................................... 11-160
Fig. 11-7: Read instance name of the GRAPH block when the PLC restarts ..................................... 11-160
Fig. 11-8: LTLP_GraphManualInputParam parameter ......................................................................... 11-161
Fig. 11-9: Call LTLP_GraphManualOutputParam ................................................................................ 11-162
Fig. 11-10: LTLP_GraphManualOutputParam parameter .................................................................... 11-162
Fig. 11-11: Parameterization of the LTLP_GraphManualSetup1Data or
LTLP_GraphManualSetup2Data....................................................................................... 11-164
Tables
Table 4-1: Setting the addresses of the MPP for IE addressing .............................................................. 4-44
Table 4-2: Setting the address at the MPP, switch S2 ............................................................................. 4-45
Table 4-3: Addressing the devices using the "logical" device names....................................................... 4-45
Table 4-4: Setting the device name at the MPP ....................................................................................... 4-45
Table 4-5: Connection identifier and UDP ports - default values.............................................................. 4-48
Table 4-6: General data in the DB7 ......................................................................................................... 4-48
Table 4-7: Parameters for the HT8 connection in the DB7 ...................................................................... 4-49
Table 4-8: Parameters for coupling direct keys in the DB7 ...................................................................... 4-50
Table 4-9: Output-Parameter LBP_OPUnitComm ................................................................................... 4-54
Table 4-10: InOut parameter LBP_OPUnitComm .................................................................................... 4-55
Table 6-1: Input parameter LTLP_ControlPanelMPP............................................................................... 6-62
Table 6-2: InOut parameter LTLP_ControlPanelMPP .............................................................................. 6-63
Table 6-3: Input parameter LTLP_ControlPanelMCP .............................................................................. 6-67
Table 6-4: InOut parameter LTLP_ControlPanelMCP.............................................................................. 6-68
Table 6-5: Input parameter LTLP_ControlPanelMPP1500....................................................................... 6-72
Table 6-6: InOut parameter LTLP_ControlPanelMPP1500 ...................................................................... 6-73
Table 6-7: Standard assignment of the MPP1500 inputs and outputs ..................................................... 6-74
Table 6-8: Input parameter LTLP_HandHeldTerminal8 ........................................................................... 6-79
Table 6-9: InOut parameter LTLP_HandHeldTerminal8 .......................................................................... 6-80
Table 6-10: Input parameter LTLP_AxisSelectScreen ............................................................................. 6-85
Table 6-11: InOut parameter LTLP_AxisSelectScreen ............................................................................ 6-85
Table 6-12: Input parameter LTLP_OperatingMode ................................................................................ 6-90
Table 6-13: InOut parameter LTLP_OperatingMode................................................................................ 6-90
Table 6-14: Input parameter LTLP_FunctionModeTransline.................................................................... 6-94
Table 6-15: InOut parameter LTLP_FunctionModeTransline ................................................................... 6-94
Table 7-1: Input parameters LTLP_DirectKey ........................................................................................ 7-111
Table 7-2: InOut parameters LTLP_DirectKey ....................................................................................... 7-111
Table 7-3: Input parameters LTLP_GetDirectKeyMoveNo ..................................................................... 7-114
Table 7-4: Output parameters LTLP_GetDirectKeyMoveNo .................................................................. 7-114
Table 7-5: InOut parameters LTLP_GetDirectKeyMoveNo .................................................................... 7-114
Table 8-1: Input parameter LTLP_CycleTime ........................................................................................ 8-118
Table 8-2: Output parameter LTLP_CycleTime ..................................................................................... 8-120
Table 8-3: InOut parameter LTLP_CycleTime ....................................................................................... 8-120
Table 8-4: Input parameter LTLP_WorkpieceCount............................................................................... 8-132
Table 8-5: Output parameter LTLP_WorkpieceCount ............................................................................ 8-134
Table 8-6: InOut parameter LTLP_WorkpieceCount .............................................................................. 8-134
Table 8-7: Output parameter LTLP_ToolLifeTime.................................................................................. 8-138
Table 8-8: InOut parameter LTLP_ToolLifeTime.................................................................................... 8-138
Table 9-1: Input parameter LTLP_SLDeviceDiagnosticCommand......................................................... 9-142
Table 9-2: InOut parameter LTLP_SLDeviceDiagnosticCommand ........................................................ 9-142
Table 11-1: Input parameter LTLP_GraphManualInputParam ............................................................. 11-161
Table 11-2: Output parameter LTLP_GraphManualInputParam .......................................................... 11-161
Table 11-3: Input parameter LTLP_GraphManualOutputParam .......................................................... 11-162
Table 11-4: Output parameter LTLP_GraphManualOutputParam ....................................................... 11-163
Table 11-5: Parameter LTLP_GraphManualSetup1Data/ LTLP_GraphManualSetup2Data ................ 11-164
1 General information
1
Uniform software structures across the TRANSLINE Solution for Powertrain assist
machine manufacturers, maintenance engineers and service personnel when
carrying out commissioning, troubleshooting and maintenance work.
The Software Guide describes the software structures for PLC and CNC-controlled
machines, as well as agreed responses to operator actions.
The Manual includes the description and handling of the HMI PRO standard
blocks for use with HMI PRO sl RT.
1.1 Preconditions
Validity
The descriptions and examples are applicable for the following versions:
SINUMERIK Operate from V04.08.x.x
TRANSLINE library from V2.1.x
TIA Portal from V14 SP1
HMI PRO sl RT from V08.x
HMI PRO CS from V08.x
In the TIA default setting, MB1 is used for the system flag and MB0 is used for the
clock cycle flag. By using the system clock cycle flag bits, it is no longer necessary
to program the symbols AlwaysTrue etc., which in STEP 7 Classic still had to be
programmed in OB1.
1.3 Blocks that are absolutely necessary when using HMI PRO
The standard blocks required for HMI PRO running under SINUMERIK Operate are
saved in the TRANSLINE library under Copy templates in directories 840evo PLC
BP and 840evo PLC BP data types.
Communication
For communication with the HT8, the DNS configuration must be parameterized in
the properties of the CPU.
LTLP_HmiProInterfaceData [DB501]
This data block represents the data interface between HMI PRO and the PLC user
program. It is saved in the TRANSLINE library under copy templates in the
common directory
In exceptional cases, the data block can also be stored in the controller under a
different number. This must be entered in the configuration tool HMI PRO CS V8
under Configuration ► Default settings ► Control via PLC ► User-defined
standard DB and subsequently activated.
2 Block overview
2
2.1 Structure of the TRANSLINE library LTLP_Transline
The TRANSLINE library comprises types and copy templates.
Types
If you are using the TRANSLINE library for the first time in your TIA project:
Open the library under Global libraries, and copy the Types directory into the
Program blocks directory of your TIA project. The folder structure from the library
is kept.
If you are already using blocks from the TRANSLINE library in your TIA project,
and wish to use a newer version:
Update the Types using the context menu ► Update project in the actual library -
or copy the Types directory to the Program blocks directory of your TIA project.
The dependencies are accepted in both cases.
Copy templates
The blocks from the copy templates are not accepted in the project when updating
the types. They must be separately copied into the project.
Attention
! In the TIA Portal – for all data blocks – on the HMI PRO accesses (direct and
indirect), the Optimized block access setting must be deselected.
For GRAPH blocks, setting Optimized block access is set as default and cannot
be changed.
DB
FB
FC
2.3 Common
General types and blocks required when using HMI PRO are contained under
Common.
Types
Copy templates
2.4 DirectKeys
Blocks that are required for the direct key screens of HMI PRO are contained under
DirectKeys.
Types
Copy templates
2.5 Graph
Blocks for step sequence processing with GRAPH are contained under Graph.
Types
Copy templates
2.6 HMIDeviceDiagnostic
Blocks for device diagnostics of HMI PRO are contained under
HMIDeviceDiagnostic.
Types
Copy templates
2.7 HMIEnergyData
Blocks that are required for the energy data screen of HMI PRO are contained
under HMIEnergyData.
Types
Copy templates
2.8 MSO
The operating mode blocks for HMI devices and switching over operating modes
are contained under MSO.
Types
Copy templates
2.9 ProductionDataAcquisition
Blocks for PDA functions lifetime overview, workpiece count, cycle times are contained
under ProductionDataAcquisition.
Types
Copy templates
For notes
3 Program structure
3
PLC program structures when using a SIMATIC S7-1500 controller are
subsequently described.
Machine manufacturers can also call up their application-specific blocks from the
management blocks, resulting in a clear and uniform program structure. If
deviations are required in the structure, they must be noted in the PLC
documentation.
Solutions for Powertrain HMI PRO sl
Interfaces DB LTLP_HMIProInterfaceData [DB501] is used for HMI PRO display
functions. The user program addresses the DB in the corresponding range in order
to implement appropriate display functions. The description of the interface bits can
be found in the online help for the HMI PRO CS configuration tool.
The blocks depicted in the program structure have the following meanings:
• Box with white background: Blocks must be supplemented or created by the
user.
• Box with gray background: Standard blocks for TRANSLINE projects.
For notes
This chapter includes information on how you connect IPCs (this involves the
IPC427 and IPC477 hardware released for SINUMERIK) with HT8, TCU and MPP
as well as a SIMATIC S7-1500 in a common network.
Fig. 4-1: Connecting an IPC and control elements to a SIMATIC S7-1500 controller
Ethernet/factory/production network
Connecting the production plants and systems to the IT landscape of an end
customer.
PN-IO network
The PN-IO network connects typical field devices with the controller of the
particular machine/station. When using intelligent field devices, by appropriately
configuring the S615, it is possible to address field devices from the system
network or the factory network.
PLC communication between the header-end and the machining units as well as
between the individual machining units is via the system network PN I-Device,
T-Send/Recv.
If the visualization data for transfer lines and flexible lines is transferred over the
system network as T:M:N applications, the system network and the PN system
network should be connected with one another using unmanaged switches. If
visualization is implemented as observation of the individual machines, it makes
sense to separate the system network and the PN system network. It is then
possible to structure each unit or cell identically; each cell has its own system
network. Only the PN system network covers the entire plant.
Fig. 4-3: Connecting an IPC and control elements to a SIMATIC PLC via the PN-2 interface
All control elements are configured in the plant/system network and the PN-2
network of the S7-1500.
• IPC, SIMATIC S7-1500 are assigned fixed addresses.
• Normally, the MPP is set as PROFINET node, and is therefore supplied with a
fixed address via the PN-2 network of the SIMATIC.
• HT8, TCUs - and possibly also the MPP - are connected via the SINUMERIK
DHCP server of the IPC. An area should be set for the IP addresses on the
IPC under Commissioning ▶Network ▶System network.
Input data (e.g. from keys) of the control components is transferred to the PLC, and
output data (e.g. LEDs) is transferred from the PLC to the control components. This
data is processed by the LTLP_ControlPanelMPP, LTLP_HandHeldTerminal8 …
blocks (see Chapter 6 Modes of Safe Operation).
The memory areas in which input and output data are saved must be defined in the
user program.
Fig. 4-4: Setting the DHCP server of the PCU for connecting HT8 to a SIMATIC PLC
The address for the HT8 must be set at the two mini rotary switches of the HT8
connection box (addressing range 1..254) – and transferred when first inserting the
HT8. The default setting is: address 14, i.e. S1=0 and S2=E.
General sequence
• Connect the HT8 to a connection module
• TCU settings
• Leave HT8 individual mode at NO
• Accept the TCU and MCP indices
• Leave the EKS index
• EnableDirect keys = YES
• No more than four HT8 handheld units can be connected or, in mixed
operation, no more than 4 nodes, consisting of TCU and HT8
The switch positions 9 and 10 guarantee the PROFINET functionality of the module
and must always be switched on.
DCP mode
No default device name is available in this mode. The device name must be set by
an "initialization procedure" and remains saved on the I/O module. It is only deleted
after a reset to factory settings, e.g. with STEP 7.
Table 4-3: Addressing the devices using the "logical" device names
1 2 3 4 5 6 7 8 9 10 Significance
on on on on on on on on on on DCP mode/PROFINET
TCU settings
• Set the TCU and MCP indices
• Leave the EKS index -> within the EKS application, the EKS index should be
entered onto the IPC, so that a data backup is available within HMI PRO.
• Set EnableDirect Keys = YES
• Enable touch capability = Yes
so that touch operation at the OP015 Black is activated
DNS configuration
The logical device names of the control components must be resolved internally into
the appropriate IP addresses. To do this, the PLC requires data relating to the DNS
server The IP address of the DNS server must be entered in the device
configuration in the properties of the CPU ▶General ▶DNS configuration. The IP
address of the plant/system interface of the IPC (X2P1) is entered as DNS server.
MCP1ConnectionId 1001
MCP2ConnectionId 1002
I HTConnectionId 1003
Op1KeyConnectionId 1004
Op2KeyConnectionId 1005
IdentConnectionId 1006
MCP1LocalUdpPort 16001
MCP2LocalUdpPort 16002
HTLocalUdpPort 16003
Op1KeyLocalUdpPort 16004
Op2KeyLocalUdpPort 16005
Note
It is not permissible to utilize the connection identifiers being used for other
communication connections in the PLC project.
It is not permissible to utilize the local UDP ports being used for other UDP
connections at this network interface in the PLC project.
Parameter Description
Fig. 4-9: Parameterization example for the general data in the DB7
Note
It is only permissible to change the data listed above when the controller restarts.
Integrating an HT8
Table 4-7: Parameters for the HT8 connection in the DB7
Parameter Description
Parameter Description
Parameter Description
OP2KeyOut from the controller to the operator component
Output address of the direct keys of the panel/HT8
For a data block, the following must be entered:
OP1KeyOut.DBNo number of the DB
OP1KeyOut.Addr pointer P#DBX0.0 as constant,
otherwise P#A0.0
Communication sequence
Communication to the machine control panels (MCP, MPP), handheld terminals
(HT) and direct key modules (OpKey) is realized via block LBP_OpUnitComm
[FB25000]. This supports simultaneous operation of up to two machine control
panels, one handheld terminal and two direct key modules via Industrial Ethernet
(IE).
Parameterization of the components is performed, as shown above, in the OB100.
Dedicated parameter sets exist for each control component. The user must define
pointers for the input and output data in these parameter sets.
Example (SCL)
// Change the configuration for MCP 1, to do this, stop MCP 1.
LBP_ConfigData.MCP1Stop := TRUE;
//Wait at least one cycle, set new parameter and start MCP 1.
LBP_ConfigData.MCP1BusAdr := 192;
LBP_ConfigData.MCP1Stop := FALSE;
// Check as to whether the connection is re-established.
IF LBP_NC.E_MCP1ready THEN
// Connection is re-established
LBP_OpUnitComm [FB25000]
Application
This block is required for communication with the SINUMERIK operator panels
(HMI devices).
For notes
Fig. 5-2: Configuring the axis selection in HMI PRO CS (PLC connection)
Activating
Activates the axis selection screen in HMI PRO RT → must be activated
General information
Entering the data block interfaces for axis selection. This is the
LTLP_NcHmiProInterfaceData [DB549] as default setting.
Block definitions
The operating mode blocks provide a similar interface for each operator panel for
the following keys and LEDs: MPP, axis selection keys and LEDs and keys/LEDs
that OEMs can freely use.
There is an FC and parameterization data block for each operator panel.
The shared interface is the LTLP_DeviceInterfaceData [DB546].
The assignment of the keys to TL and NC functions is defined in each case for the
associated parameterization data block.
Fig. 6-1: Program structure when using a MPP, MCP, HT8 or the U keys screen with a
SIMATIC PLC
ENABLE Bool Global release for reading in the function and key
signals of the MPP483.
This must be set to TRUE if this is the active operating
panel.
RESTART_PLC Bool First block cycle following a CPU restart.
This must be done after every reparameterization of
the key interface in LTLP_ControlPanelMPPData
[DB540]. According to the TRANSLINE standard, the
FirstScan [M1.0] flag is specified here.
LAMPTEST Bool Lamp test, all outputs (lamps and LEDs) are controlled
with this signal.
This is the LTLP_HMIProInterfaceData.pLamptest as
default setting.
ACTIVAT_KEY_SWITCH Bool TRUE for MPP with protection level key-operated
switch
PTR_INPUT_SIGNALS Variant Pointer to the input signals of the MPP483.
Dependencies
none
Possible variables
Inputs: parameterizationInputs area
Outputs parameterizationOutputs area
mppComponent:
machineOn STRING[4] TRANSLINE function unit/
Machine on
machineOff STRING[4] TRANSLINE function unit/
Machine off
mediaOn STRING[4] TRANSLINE function media ON
mediaOff STRING[4] TRANSLINE function media off
basicPosition STRING[4] TRANSLINE function initial state
startJog STRING[4] TRANSLINE function start/jog single
step
acknowledgeFault STRING[4] TRANSLINE function acknowledge fault
faultWillBeCorrected STRING[4] Message to TRANSLINE Collect/VW
Master Interface/PRISMA
allUnitsBack STRING[4] TRANSLINE function all units back
stopAfterEndOfCycle STRING[4] TRANSLINE function stop after end of
cycle
immediateStop STRING[4] TRANSLINE function immediate stop
lockRelProtectDoors STRING[4] TRANSLINE function lock/release
protective doors
emergencyStop STRING[4] Emergency Off
automaticMode STRING[4] TRANSLINE function automatic mode
(AUT)
singleMode STRING[4] TRANSLINE function single mode SM
singleStepMode STRING[4] TRANSLINE function single step mode
SSM
setupMode STRING[4] TRANSLINE function setup mode SET
mppComponent:
auto STRING[4] NC function AUTO
mda STRING[4] NC function MDA
teach STRING[4] NC function TEACH
jog STRING[4] NC function JOG
singleBlock STRING[4] NC function SINGLE BLOCK
increment1 STRING[4] NC function increment 1
increment10 STRING[4] NC function increment 10
increment100 STRING[4] NC function increment 100
increment1000 STRING[4] NC function increment 1000
increment10000 STRING[4] NC function increment 10000
incrementVariable STRING[4] NC function variable increments
gotoRefpoint STRING[4] NC function goto reference point
repos STRING[4] NC function REPOS
ncStop STRING[4] NC function NC STOP
ncStart STRING[4] NC function NC start
feedStop STRING[4] NC function feed stop
feedStart STRING[4] NC function feed start
spindleStop STRING[4] NC function spindle stop
spindleStart STRING[4] NC function spindle start
axisSelectionByHMI STRING[4] NC fct. axis selection screen HMI PRO
mcsWcs STRING[4] NC function switchover request
MCS/WCS
oem:
oem[1] STRING[4] Unassigned function key for OEM
.
.
oem[100] STRING[4] Unassigned function key for OEM
Assigning keys and functions is realized by entering the key designation from Fig.
6-4 into the string, which is assigned to the function:
ENABLE Bool Global release for reading in the function and key
signals of the MCP483.
This must be set to TRUE if this is the active operating
panel.
RESTART_PLC Bool First block cycle following a CPU restart.
This must be done after every reparameterization of
the key interface in LTLP_ControlPanelMCPData
[DB541]. According to the TRANSLINE standard, the
FirstScan [M1.0] flag is specified here.
LAMPTEST Bool Lamp test, all outputs (lamps and LEDs) are controlled
with this signal.
This is the LTLP_HMIProInterfaceData.pLamptest as
default setting.
ACTIVAT_KEY_SWITCH Bool TRUE for MCP with protection level key-operated
switch
Dependencies
none
Possible variables
Inputs: parameterizationInputs area
Outputs parameterizationOutputs area
mppComponent:
machineOn STRING[4] TRANSLINE function unit/
Machine on
machineOff STRING[4] TRANSLINE function unit/
Machine off
mediaOn STRING[4] TRANSLINE function media ON
mediaOff STRING[4] TRANSLINE function media off
basicPosition STRING[4] TRANSLINE function initial state
startJog STRING[4] TRANSLINE function start/jog single
step
acknowledgeFault STRING[4] TRANSLINE function acknowledge fault
faultWillBeCorrected STRING[4] Message to TRANSLINE Collect/VW
Master Interface/PRISMA
allUnitsBack STRING[4] TRANSLINE function all units
back
stopAfterEndOfCycle STRING[4] TRANSLINE function stop after end of
cycle
immediateStop STRING[4] TRANSLINE function immediate stop
lockRelProtectDoors STRING[4] TRANSLINE function lock/release
protective doors
emergencyStop STRING[4] Emergency Off
automaticMode STRING[4] TRANSLINE function automatic mode
(AUT)
singleMode STRING[4] TRANSLINE function single mode SM
mppComponent:
auto STRING[4] NC function AUTO
mda STRING[4] NC function MDA
teach STRING[4] NC function TEACH
jog STRING[4] NC function JOG
singleBlock STRING[4] NC function SINGLE BLOCK
increment1 STRING[4] NC function increment 1
increment10 STRING[4] NC function increment 10
increment100 STRING[4] NC function increment 100
increment1000 STRING[4] NC function increment 1000
increment10000 STRING[4] NC function increment 10000
incrementVariable STRING[4] NC function variable increments
gotoRefpoint STRING[4] NC function goto reference point
repos STRING[4] NC function REPOS
ncStop STRING[4] NC function NC STOP
ncStart STRING[4] NC function NC start
feedStop STRING[4] NC function feed stop
feedStart STRING[4] NC function feed start
spindleStop STRING[4] NC function spindle stop
spindleStart STRING[4] NC function spindle start
axisSelectionByHMI STRING[4] NC fct. axis selection screen HMI PRO
mcsWcs STRING[4] NC function switchover request
MCS/WCS
reset STRING[4] NC function reset
rapid STRING[4] NC function rapid traverse
motionPlus STRING[4] NC function motion plus direction
motionMinus STRING[4] NC function motion minus direction
axis:
axis[1] STRING[4] NC function axis selection
.
.
axis[31] STRING[4] NC function axis selection
oem:
oem[1] STRING[4] Unassigned function key for OEM
.
.
oem[100] STRING[4] Unassigned function key for OEM
Assigning keys and functions is realized by entering the key designation from Fig.
6-8 into the string, which is assigned to the function:
ENABLE Bool Global release for reading in the function and key
signals of the MPP1500.
This must be set to TRUE if this is the active operating
panel.
RESTART_PLC Bool First block cycle following a CPU restart. This must be
done after every reparameterization of the key
interface in LTLP_ControlPanelMPP1500Data
[DB544]. According to the TRANSLINE standard, the
FirstScan [M1.0] flag is specified here.
LAMPTEST Bool Lamp test, all outputs (lamps and LEDs) are controlled
with this signal.
PTR_INPUT_SIGNALS Variant Pointer to the input signals of the MPP1500.
Dependencies
none
Possible variables
Inputs: parameterizationInputs area
mppComponent:
machineOn STRING[4] TRANSLINE function unit/
Machine on
machineOff STRING[4] TRANSLINE function unit/
Machine off
mediaOn STRING[4] TRANSLINE function media on
mediaOff STRING[4] TRANSLINE function media off
basicPosition STRING[4] TRANSLINE function initial state
startJog STRING[4] TRANSLINE fct. start/jog single step
acknowledgeFault STRING[4] TRANSLINE function acknowledge fault
faultWillBeCorrected STRING[4] Message to TRANSLINE Collect/VW
Master Interface/PRISMA
allUnitsBack STRING[4] TRANSLINE function all units back
stopAfterEndOfCycle STRING[4] TRANSLINE function stop after end of
cycle
immediateStop STRING[4] TRANSLINE function immediate stop
lockRelProtectDoors STRING[4] TRANSLINE function lock/release
protective doors
emergencyStop STRING[4] Emergency Off
automaticMode STRING[4] TRANSLINE function automatic mode
(AUT)
singleMode STRING[4] TRANSLINE function single mode SM
singleStepMode STRING[4] TRANSLINE function single step mode
SSM
setupMode STRING[4] TRANSLINE function setup mode SET
mppComponent:
auto STRING[4] NC function AUTO
mda STRING[4] NC function MDA
teach STRING[4] NC function TEACH
jog STRING[4] NC function JOG
singleBlock STRING[4] NC function SINGLE BLOCK
increment1 STRING[4] NC function increment 1
increment10 STRING[4] NC function increment 10
increment100 STRING[4] NC function increment 100
increment1000 STRING[4] NC function increment 1000
increment10000 STRING[4] NC function increment 10000
incrementVariable STRING[4] NC function variable increments
gotoRefpoint STRING[4] NC function goto reference point
repos STRING[4] NC function REPOS
ncStop STRING[4] NC function NC STOP
ncStart STRING[4] NC function NC start
feedStop STRING[4] NC function feed stop
feedStart STRING[4] NC function feed start
spindleStop STRING[4] NC function spindle stop
spindleStart STRING[4] NC function spindle start
axisSelectionByHMI STRING[4] NC function axis selection screen
HMI PRO
mcsWcs STRING[4] NC function switchover request
MCS/WCS
reset STRING[4] NC function reset
oem:
oem[1] STRING[4] Unassigned function key for OEM
.
.
oem[100] STRING[4] Unassigned function key for OEM
mppComponent:
machineOn LTLP_typeParamMPP1500Output TRANSLINE function
unit/
Machine on
machineOff LTLP_typeParamMPP1500Output TRANSLINE function
unit/
Machine off
mediaOn LTLP_typeParamMPP1500Output TRANSLINE function
media ON
mediaOff LTLP_typeParamMPP1500Output TRANSLINE function
media off
basicPosition LTLP_typeParamMPP1500Output TRANSLINE function
initial state
: : :
: : :
Keys and functions are assigned to one another by entering the key designation
from Fig. 6-12 into the string to which the function is assigned:
ENABLE Bool Global release for reading in the function and key
signals of the HT8.
This must be set to TRUE if this is the active HHU.
RESTART_PLC Bool First block cycle following a CPU restart. This must be
done after every reparameterization of the key
interface in LTLP_HandHeldTerminal8Data [DB542].
According to the TRANSLINE standard, the FirstScan
[M1.0] flag is specified here.
LAMPTEST Bool Lamp test, all outputs (LEDs) are controlled with this
signal.
PTR_INPUT_SIGNALS Variant Pointer to the input signals of the HT8.
Dependencies
none
Possible variables
Inputs: parameterizationInputs area
Outputs parameterizationOutputs area
mppComponent:
machineOn STRING[4] TRANSLINE function unit/
Machine on
machineOff STRING[4] TRANSLINE function unit/
Machine off
mediaOn STRING[4] TRANSLINE function media ON
mediaOff STRING[4] TRANSLINE function media off
basicPosition STRING[4] TRANSLINE function initial state
startJog STRING[4] TRANSLINE function start/jog single
step
acknowledgeFault STRING[4] TRANSLINE function acknowledge fault
faultWillBeCorrected STRING[4] Message to TRANSLINE Collect/VW
Master Interface/PRISMA
allUnitsBack STRING[4] TRANSLINE function all units back
stopAfterEndOfCycle STRING[4] TRANSLINE function stop after end of
cycle
immediateStop STRING[4] TRANSLINE function immediate stop
lockRelProtectDoors STRING[4] TRANSLINE function lock/release
protective doors
emergencyStop STRING[4] Emergency Off
automaticMode STRING[4] TRANSLINE function automatic mode
(AUT)
singleMode STRING[4] TRANSLINE function single mode SM
singleStepMode STRING[4] TRANSLINE function single step mode
SSM
setupMode STRING[4] TRANSLINE function setup mode SET
Assigning keys and functions is realized by entering the key designation from
Fig. 6-16 into the string, which is assigned to the function:
ENABLE Bool Global enable to read-in the function and key signals of
the U keys screen.
This should be set to TRUE if this screen is active.
RESTART_PLC Bool First block cycle following a CPU restart. This must be
done after every reparameterization of the key
interface in LTLP_AxisSelectScreen [DB545].
According to the TRANSLINE standard, the FirstScan
[M1.0] flag is specified here.
LAMPTEST Bool Lamp test, all outputs (LEDs shown in the screen) are
activated using this signal.
Dependencies
none
Possible variables
Inputs: parameterizationInputs area
Outputs parameterizationOutputs area
mppComponent:
machineOn STRING[4] TRANSLINE function unit/
Machine on
machineOff STRING[4] TRANSLINE function unit/
Machine off
mediaOn STRING[4] TRANSLINE function media ON
mediaOff STRING[4] TRANSLINE function media off
basicPosition STRING[4] TRANSLINE function initial state
startJog STRING[4] TRANSLINE function start/jog single
step
acknowledgeFault STRING[4] TRANSLINE function acknowledge
fault
faultWillBeCorrected STRING[4] Message to TRANSLINE Collect/VW
Master Interface/PRISMA
allUnitsBack STRING[4] TRANSLINE function all units back
stopAfterEndOfCycle STRING[4] TRANSLINE function stop after end
of cycle
immediateStop STRING[4] TRANSLINE function immediate stop
lockRelProtectDoors STRING[4] TRANSLINE function lock/release
protective doors
Assigning keys and functions is realized by entering the key designation from Fig.
6-20 into the string, which is assigned to the function:
Dependencies
None
LTLP_OperatingModeData [DB547]
The locking of the key functions takes place in this data block at the device
interface LTLP_DeviceInterfaceData [DB546]; i.e. impermissible keys are
suppressed by this block. There are interlocks from
mcpFunctions
auto Bool NC function AUTO
mda Bool NC function MDA
teach Bool NC function TEACH
jog Bool NC function JOG
singleBlock Bool NC function SINGLE BLOCK
increment1 Bool NC function increment 1
increment10 Bool NC function increment 10
increment100 Bool NC function increment 100
increment1000 Bool NC function increment 1000
increment10000 Bool NC function increment 10000
incrementVariable Bool NC function variable increments
gotoRefpoint Bool NC function goto reference point
repos Bool NC function REPOS
ncStop Bool NC function NC STOP
ncStart Bool NC function NC start
feedStop Bool NC function feed stop
feedStart Bool NC function feed start
spindleStop Bool NC function spindle stop
spindleStart Bool NC function spindle start
axisSelectionByHMI Bool NC function axis selection screen
HMI PRO
mcsWcs Bool NC function switchover request
MCS/WCS
reset Bool NC function reset
rapid Bool NC function rapid traverse
motionPlus Bool NC function motion plus direction
motionMinus Bool NC function motion minus direction
nextAxis Bool key next axis
previousAxis Bool key previous axis
handwheelActive Bool Handwheel selected
axes
axis[1] Bool NC function axis selection
.
.
axis[31] Bool NC function axis selection
oemFunctions
oemFunctions[1] Bool Unassigned function key for OEM
.
.
oemFunctions[100] Bool Unassigned function key for OEM
DEVICE_ LTLL_typeDevice The interface between the operator panels and the
INTERFACE Interface blocks for acquiring the operating modes and the
TRANSLINE functions.
This is the LTLP_DeviceInterfaceData [DB546] as
default setting.
Dependencies
None
• Single mode
When singleMode is selected in the LTLP_DeviceInterfaceData, inputs
area, then LTLP_FunctionModeTransline sets data bit
LTLP_HMIProInterfaceData.pSingleMode [DBX76.2].
With single mode active, the user must acknowledge this bit with bit
LTLP_HMIProInterfaceData.singleMode [DBX86.2].
Bit singleMode in the LTLP_DeviceInterfaceData, outputs.mppFunctions
area, flashes until bit LTLP_HMIProInterfaceData.singleMode [DBX86.2]
assumes a status of 1 - after which time, it is continuously activated.
When bit LTLP_HMIProInterfaceData.singleMode [DBX86.2] is set then in
the header, the symbol is activated.
• Single step
When singleStepMode is selected in the LTLP_DeviceInterfaceData, inputs
area, then LTLP_FunctionModeTransline sets data bit
LTLP_HMIProInterfaceData.pSingleStepMode [DBX76.3].
With single step mode active, the user must acknowledge this bit with bit
LTLP_HMIProInterfaceData.singleStepMode [DBX86.3].
Bit pSingleStepMode in the LTLP_DeviceInterfaceData,
outputs.mppFunctions area, flashes until bit
LTLP_HMIProInterfaceData.singleStepMode [DBX86.3] assumes a status of
1 – after which time, it is continuously activated.
When bit LTLP_HMIProInterfaceData.singleStepMode [DBX86.3] is set then
in the header, the symbol is activated.
• Setup
When setupMode is selected in the LTLP_DeviceInterfaceData, inputs area,
then LTLP_FunctionModeTransline sets data bit
LTLP_HMIProInterfaceData.pSetupMode [DBX76.4].
With setup active, the user must acknowledge this bit with bit
LTLP_HMIProInterfaceData.setupMode [DBX86.4].
Bit setupMode in the LTLP_DeviceInterfaceData, outputs.mppFunctions
area, flashes until bit LTLP_HMIProInterfaceData.setupMode [DBX86.4]
assumes a status of 1 - after which time, it is continuously activated.
When bit LTLP_HMIProInterfaceData.setupMode [DBX86.4] is set then in
the header, the symbol is activated.
• Machine/unit on
Using bit machineOn in the LTLP_DeviceInterfaceData, inputs area, with
the LTLP_FunctionModeTransline bit
LTLP_HMIProInterfaceData.pMachineOn [DBX77.7] is set, bit
LTLP_HMIProInterfaceData.pMachineOff [DBX76.6] is reset. machineOn in
the LTLP_DeviceInterfaceData, outputs.mppFunctions area flashes.
Once the machine has been switched on, the user sets bit
LTLP_HMIProInterfaceData.machineUnitOn [DBX87.6].
machineOn in the LTLP_DeviceInterfaceData, outputs.mppFunctions
area, now displays a continuous one
• Machine/unit off
Using the bit machineOff in the LTLP_DeviceInterfaceData, inputs area, the
LTLP_FunctionModeTransline bit
LTLP_HMIProInterfaceData.pMachineOff [DBX76.6] is set, bit
LTLP_HMIProInterfaceData.pMachineOn [DBX77.7] is reset.
Once the machine has been switched off, the user sets bit
LTLP_HMIProInterfaceData.machineUnitOff [DBX87.7].
• Initial state
With bit basicPosition in the LTLP_DeviceInterfaceData, inputs area,
LTLP_HMIProInterfaceData.pBasicPosition [DBX77.6] is set using the
LTLP_FunctionModeTransline bit.
The machine manufacturer sets bit
LTLP_HMIProInterfaceData.gotoBasicPosition [DBX86.6] as response. By
setting this bit, basicPosition in the LTLP_DeviceInterfaceData, outputs
area starts to flash. Using bit
LTLP_HMIProInterfaceData.reachedBasicPosition [DBX86.7], the
continuous signal basicPosition signals that the machine is in basic position.
Bits LTLP_HMIProInterfaceData.pBasicPosition and
LTLP_HMIProInterfaceData.gotoBasicPosition must be reset.
• Start/jog
The signal start_jog in the LTLP_DeviceInterfaceData, inputs area, is used
for starting the interlinked mode, single mode or single step mode.
Signal startJog controls bit LTLP_HMIProInterfaceData.pStart [DBX77.5].
Signal startJog in the LTLP_DeviceInterfaceData, outputs.mppFunctions
area, starts to flash by controlling bits
LTLP_HMIProInterfaceData.readyAutomaticStart [DBX89.4] or
LTLP_HMIProInterfaceData.selStopAfterEndOfCycle [DBX87.2]. If bit
LTLP_HMIProInterfaceData.startJog [DBX87.2], is set, then the signal is
permanently one:
• Acknowledge fault
Signal LTLP_HMIProInterfaceData.pGroupAcknowledge [DBX78.0] can be
reached using signal acknowledgeFault in the LTLP_DeviceInterfaceData,
inputs.mppFunctions area, as well as using input parameter EXT_ACKN.
When faults such as LTLP_HMIProInterfaceData.completeMachineFault
[DBX88.5] or LTLP_HMIProInterfaceData.generalFault [DBX88.2] or
LTLP_HMIProInterfaceData.executionFault [DBX88.3] occur, then the signal
acknowledgeFault in the LTLP_DeviceInterfaceData,
outputs.mppFunctions area, starts to flash.
• Immediate stop
With the request Bit immediateStop in the LTLP_DeviceInterfaceData,
inputs area, bit LTLP_HMIProInterfaceData.pImmediateStop [DBX81.1] is
set.
The user acknowledges this using bit
LTLP_HMIProInterfaceData.immediateStop [DBX87.1].
As long as this bit is equal to 1, then immediateStop in the
LTLP_DeviceInterfaceData, outputs.mppFunctions area, is controlled.
• Emergency stop
Using bit emergencyStop in the LTLP_DeviceInterfaceData, inputs area, bit
LTLP_HMIProInterfaceData.pEmergencyStop [DBX77.3] is set to 1.
• Protective doors
With request lockRelProtectDoors in the LTLP_DeviceInterfaceData,
inputs area, bit LTLP_HMIProInterfaceData.pLockReleaseProtectDoors
[DBX81.4] is set to 1.
If it is possible to lock or unlock the protective doors, the user must
acknowledge the selection with bit
LTLP_HMIProInterfaceData.selectProtectionDoors [DBX70.0]. If bit
LTLP_HMIProInterfaceData.selectProtectionDoors [DBX70.0] has a status
of 1, then the lockReleaseProtectDoors signal in the
LTLP_DeviceInterfaceData, outputs.mppFunctions area flashes.
If the user sets bit LTLP_HMIProInterfaceData.lockReleaseProtectDoors
[DBX95.6] to 1 (protective doors are released), then the lamp/LED is
continually lit.
After the execution – or when execution is not possible – the user must reset
the LTLP_HMIProInterfaceData.selectProtectionDoors (DBX70.0) bit.
Fig. 7-2: Direct keys: Using the HT8, OP08T, OP015 Black, TCU + OP
The configuration and sequence are subsequently displayed using a setup function
(setup screen 1).
Inserting a setup screen into the function key assignment
This is realized in HMI PRO CS via Project navigation ▶Function key
assignment. From the Screen scope ▶Direct keys, drag setup screen 1 and
drop on the required key in the function key assignment. You can define the
designation of the movement group using the right-hand mouse key and the
context menu Change function key labeling.
Configuring dialog setup screen
Via Project navigation ▶Function key assignment ▶Setup. 1 or by double-
clicking on the function key, open the configuration dialog for direct key screens.
On the right-hand side below Properties ▶Screen you define how you wish to
arrange setup movements.
Fig. 7-4: Configuring setup screens in HMI PRO CS: Properties ▶Screen
Fig. 7-5: Configuring setup screens in HMI PRO CS: Movement properties
The properties for movement active, end positions etc. are defined under
Properties ▶ Left or Right.
Fig. 7-7: Configuring setup screens in HMI PRO CS: Properties, left
Fig. 7-8: Supply of the direct key screens (example for the 1st direct key left '-')
Fig. 7-9: Call sequence for direct key screens in the controller
Block LTLP_DirectKey [FC511] must be called once. The formal parameters are
supplied depending on the active operator panel. See also Chapter 5.1.
Attention
LTLP_DirectKey [FC511] must be used for direct key screens.
The function block represents the link between the direct keys of the operator panel
and the data bar of HMI PRO LTLP_HMIProInterfaceData. It is required for all
screens that use direct keys.
In conjunction with HMI PRO, this block determines the function code for the
appropriate selected movement or direct key function.
HMI_DB LTLP_typeHMIPro Interface between HMI PRO and PLC user program.
Interface Data block LTLP_HMIProInterfaceData [DB501] should be
used here as variable.
Data interface
There is a transfer area for the direct keys in the LTLP_HMIProInterfaceData data
bar. This area is used to transfer the pressed direct key as well as the bits for the
+/- movement to the operator panels and calculate the actual line number. This line
number is signaled to the user via DBW79 and a lock bit is set.
This function can be deactivated with parameter PLUS_MINUS_EXTERN=TRUE
in order to connect the standard plus/minus function to external keys. If
PLUS_MINUS_EXTERNAL is set to FALSE, then the plus/minus keys are realized
with HMI PRO and the LTLP_DirectKey.
Note
Please note that the movement number must be interpreted as word, is
BCD-coded and low/high are interchanged.
The programming resources that implement the functions are only allocated after
the LTLP_DirectKey. The use of GRAPH is described in Chapter 9.
Application
For the direct key functions, this block is used to convert the function number from
HMI PRO LTLP_HMIProInterfaceData.noFunctionLow [DBB79] and
LTLP_HMIProInterfaceData.noFunctionHigh [DBB80] into a bit.
HMI_DB LTLP_typeHMIPro Interface between HMI PRO and PLC user program.
Interface LTLP_HMIProInterfaceData [DB501] is the default
setting.
HMI_DECODE_ LTLP_typeDirectK Bit interface between the user and the direct keys
DB eyGetMoveNo Data block LTLP_DirectKeyGetMovNoData [DB512]
should be used here as variable.
Data interface
From the data bar LTLP_HMIProInterfaceData, the movement number comprising
LTLP_HMIProInterfaceData.noFunctionLow [DBB79] and
LTLP_HMIProInterfaceData.noFunctionHigh [DBB80] is used. From this
number, a data bit in data block LTLP_DirectKeyGetMovNoData is determined.
This means from the value of the 1st movement of the setup screen 1 (BCD code
101) data bit LTLP_DirectKeyGetMovNoData.Setup1[1] is obtained.
8 PDA functions
8
Under the general term, PDA functions, for HMI PRO, the following screens are
involved:
• Cycle times
• Workpiece count
• Utilization
• Shift model
• Tool life overview
• Tool wear
For the Cycle times, Workpiece count and Lifetime overview screens the
required standard blocks are stored in the TRANSLINE library in the
ProductionDataAcquisition folder.
The Machine utilization and Shift model screens do not require any blocks.
The tool wear screen is a screen from the SINUMERIK standard and is described
the.
Fig. 8-2
The user must enter the target cycle time for the entire machine and the target
cycle times for the machining units in the LTLP_HMIProInterfaceData in
1/10 seconds ("LTLP_HMIProInterfaceData".targetCycleTimeCompleteMach,
"LTLP_HMIProInterfaceData".targetCycleTime[X]).
Fig. 8-2
The LTLP_CycleTime block must be called once for the entire machine
(parameter MACHINING_UNIT = 0) and once for each displayed machining unit
(parameter MACHINING_UNIT = X).
Fig. 8-2
Depending on parameter MACHINING_UNIT, the FB writes the actual cycle times
of the complete machine or the actual cycle times of machining units to
LTLP_HMIProInterfaceData.
("LTLP_HMIProInterfaceData".targetCycleTimeCompleteMach or
"LTLP_HMIProInterfaceData".targetCycleTime [X]).
Fig. 8-2
HMI PRO displays the values from LTLP_HMIProInterfaceData in the Cycle times
screen. If the actual value exceeds the specified setpoint, its color turns red.
LTLP_CycleTime [FB523]
Application
This block is required for the Cycle times HMI PRO screen.
Data interface
The actual cycle times are supplied in data area LTLP_HMIProInterfaceData
("LTLP_HMIProInterfaceData".targetCycleTimeCompleteMach to
"LTLP_HMIProInterfaceData".targetCycleTime[40]).
MACHINING_UNIT Int Unit/machine for which the cycle time should be calculated:
1 to 40: Number of the machining unit
0: Complete machine
RESTART_PLC Bool Initializes all machining units of the instance; this is applied
when the CPU reboots
For TRANSLINE: Bit memory FirstScan (M1.0)
START Bool If the time is acquired using START/STOP, then the formal
START_STOP parameter must be assigned AlwaysFalse.
Acquisition is started with a positive edge at START.
Another positive edge without a previous STOP causes the
cycle time acquisition to restart. The time that has
accumulated up until then is discarded.
STOP Bool If the time is acquired using START/STOP, then the formal
START_STOP parameter must be assigned AlwaysFalse.
The acquisition is stopped with a positive edge if the
acquisition was previously started using "START". An
additional positive edge without a previous START has no
effect.
The acquisition of the cycle times is started by the positive
edge at "START_END". The measurement is terminated by
a negative edge at "START_STOP". Measurement is only
performed when HOLD is not set.
HMI_DB LTLP_typeHmi Interface between HMI PRO and PLC user program.
ProInterface As default setting, this is the LTLP_HMIProInterface
[DB501] from the copy template.
Attention
! Parameters that are not connected must be set to AlwaysFalse.
If multiple calls are made, the block must always be supplied the same instance
data block.
Fig. 8-7: Relationship between type preselection, workpiece overview and part counter
Only with these settings can you see the relevant absolute addresses that you
have to enter in HMI PRO CS.
Note
The TRANSLINE blocks and examples only support eight workpieces with the
same name per station.
The Workpiece overview screen shows the workpiece types available for each
station, plus the status of the workpieces (good/scrap). Each workpiece is
visualized using the following displays:
• Workpiece code (can be optionally hidden)
• Workpiece type
• Workpiece correct/not correct
• Workpiece present/not present
• Extended workpiece status (see online help for HMI PRO sl RT)
Note
Regarding the display of workpiece types and codes, please note that LOW and
HIGH bytes are swapped for workpiece types, as they are for type preselection.
The workpiece type is BCD-coded. If the workpiece type in the stations is
machined using the workpiece code, please note that the workpiece code is
stored as an integer value.
Transferring the type from type preselection with type number in the Code field
to station 1
Copies the data for the workpiece overview
"LTLP_HMIProInterfaceData".workpieceTypeStation[1]
Depending on the number of workpieces of the same name, the bits must be set
as code in "LTLP_HMIProInterfaceData".station[1].
IF ("mipStartTypTransfer")
THEN
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].workpieceType :=
"LTLP_HMIProInterfaceData".workpiecetypeLoadingBelt;
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].typeAPresent := true;
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].typeAOk := true;
"LTLP_HMIProInterfaceData".station[1] := BCD32_TO_DINT(IN :=
SWAP("LTLP_HMIProInterfaceData".workpieceTypeStation[1].workpieceType));
END_IF;
Transferring the type number from a data storage medium with type number in
the Code field
When using the codes from the data storage medium, reading the type of the type
identifier no longer applies. The type number from the data storage medium is
written to data word
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].workpieceType.
Transferring the type from type preselection with workpiece code to station 1
When using the code from a data storage medium, the transfer of the
type preselection could look like the following.
IF ("mipStartTypTransfer")
THEN
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].workpieceType :=
"LTLP_HMIProInterfaceData".workpiecetypeLoadingBelt;
"HMI_interface".typNo := BCD32_TO_DINT(IN :=
SWAP("LTLP_HMIProInterfaceData".workpieceTypeStation[1].workpieceType));
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].typeAPresent := true;
"LTLP_HMIProInterfaceData".workpieceTypeStation[1].typeAOk := true;
// Determine workpiece code
IF ("HMI_interface".typNo <= 32)
THEN
"LTLP_HMIProInterfaceData".station[1] :=
"LTLP_HMIProInterfaceData".typePreselectWorkpieceCode["HMI_interface ".typNo];
ELSE
"LTLP_HMIProInterfaceData".station[1] :=
"HMI_interface".WorkpieceCode["HMI_interface".typNo]
END_IF
END_IF;
From this point, the user can change workpiece OK / workpiece not OK,
available/unavailable or the workpiece code.
Workpiece OK / workpiece not OK and the workpiece code can be changed by the
user on the workpiece overview screen. The PLC programmer is informed about
the workpiece status (e.g. OK/not OK and workpiece code) using data bytes
noFunctionLow and noFunctionHigh in the LTLP_HMIProInterfaceData
[DBW79]. Since this data word is used for transferring from several screens, the
evaluation of the data word must always be locked using the screen ID or screen
number (see HMI PRO CS online help).
Note
In the PLC, this part of the workpiece overview is only possible based on pointer
addressing. The data connection to HMI PRO does not allow any other
possibility.
The workpiece properties can be changed using the plus key to indicate
"workpiece OK" or "available", or the minus key to indicate "workpiece not OK" or
"unavailable".
//Check keys
UN "LTLP_HMIProInterfaceData“.Pplus // (DBX77.1)
UN "LTLP_HMIProInterfaceData“.Pminus // (DBX77.2)
JC cod1
bit: NOP 0
L #stationNo //(tempVar)
SLW 5 //*24
LAR1 P#1558.0 //Start address workpiece properties
+AR1 //Address station workpiece properties
L #Bit number
+AR1 //Bit address of the workpiece property
U "LTLP_HMIProInterfaceData".Pplus
S DBX [AR1,P#0.0]
U "LTLP_HMIProInterfaceData".Pminus
R DBX [AR1,P#0.0]
cod1: NOP 0
IF ("LTLP_HMIProInterfaceData".noScreenId = 23)
THEN
IF ("LTLP_HMIProInterfaceData".noFunctionHigh = W#16#61)
THEN
// Workpiece code changed
"LTLP_HMIProInterfaceData".station [(BCD16_TO_INT
("LTLP_HMIProInterfaceData".noFunctionLow)-40)] :=
"LTLP_HMIProInterfaceData".codeWorkpiece ;
END_IF
END_IF;
Fig. 8-9: Interrelationship between the screen Workpiece count and block LTLP_WorkpieceCount
Note
The workpiece counter type (preselWorkpieceCountReset), which should be
reset, is BCD-coded and LOW/HIGH are interchanged.
LTLP_WorkpieceCount [FB522]
This block is required for the Workpiece count HMI PRO screen.
The workpieces machined in the machine are counted using this block. Up to 1000
workpiece types with a maximum of 8 workpieces are possible per station.
(Configuring in the workpiece overview screen under Properties)
Workpieces are counted each shift, each day and over the entire period. Every
counter indicates the sum of all workpieces as well as correct and incorrect
workpieces. The counters can be reset.
Application
This block is required for the Workpiece count HMI PRO screen.
Data interface
For a type number <= 32, the data area in LTLP_HMIProInterfaceData (from
cntTotalWorkpieces up to cntWorkpiecetype[32]) is supplied. As data source, a
structure is taken from "LTLP_HMIProInterfaceData".workpieceTypeStation[],
which refers to parameter STATION_INDEX. For a type number > 32, parameter
EXTERNAL_COUNTER_DB must be supplied with an array, type
LTLP_typeWorkpieceCount.
MACHINING_UNIT Int Number of the machining unit (1 to 40), whose workpiece type
should be counted
This is a reference to the following structure within the HMI PRO
interface LTLP_HMIProInterfaceData:
The counter values for a maximum of 96 tool groups are managed and stored in
the controller. The counter values for the actual value, pre-alarm, alarm and
extended alarm are listed in the LTLP_HMIProInterfaceData using the
LTLP_ToolLifeTime (FB521).
Further, the alarm status and the activation of the lifetime extension of a tool group
are also displayed.
Application
This block supplies the lifetime screens in the TRANSLINE environment.
Data interface
The block supplies areas "LTLP_HMIProInterfaceData".toolGroup and
"LTLP_HMIProInterfaceData".identification96Extended of the HMI PRO data
area.
Block description
Up to 99,999,999 machining cycles can be counted per tool group. The block
processes as many as 96 tool groups. Each tool group receives its own counting
pulse and reports the current status of the tool group to the user program.
Responses to TOOL_STATE
The machine responds to workpiece lifetime alarms in accordance with this table.
For notes
Virtual stations
With the aid of the configuration of virtual stations, it is possible to visualize up to
20 stations on the operator panel with one controller. This means that a station is
the virtual image of a PLC on the actual SIMATIC PLC controller. A separate
HMI PRO DB with a different number is generated for each station to be visualized.
Permissible operator components are: one IPC with one MPP or HT8.
An HMI PRO project with virtual stations contains a basic configuration (ROOT)
and, for each station to be visualized, a station-specific configuration in a dedicated
data block. As a consequence, virtual stations operate with a multitude of standard
HMI PRO DBs on a controller.
Virtual stations are only permitted for a 1:1 connection.
1:N projects are designated with in the status list.
Fig. 10-5: Possible configurations of the controller texts in the function key menu
Fig. 10-6: Configuration and data variable using setup screen 1 as example
Fig. 10-7: Configuration static and data variable using setup screen 1 as example
Fig. 10-8: Configuration and data from controller PLC1 using setup screen 1 as example
Creating a project with virtual stations from a standard project (1:1 assignment)
1. Create a standard project (1:1 assignment)
2. In the project navigation, under Controller ▶ Controller connection
▶ Basic connection, activate checkbox Project with virtual stations
(separate DBs).
3. Under Controller ▶ Configuration of the virtual stations configure all
HMI PRO DBs that you wish to use in your project with virtual stations.
Your project with virtual stations is created, and the standard project that
you created in step 1, is accepted as ROOT configuration and is copied to
all station-specific configurations.
The field Configuration and data connection is displayed in the window
Properties of the function key under the Global tab.
4. To configure the virtual stations, click on the required function keys one
after the other, and then copy these to a free function key.
5. In dialog Assignment function key 'Screen name', select the
configuration and data connection for the copied screen; i.e. which
configuration and which data should be displayed after switching over to
another station in HMI PRO RT.
The following configurations are available in the dialog:
If you use the controller blocks from TRANSLINE, then you must ensure
that parameter HMI_DB must be supplied/parameterized with the HMI-
PRO DB (number) of the currently selected station.
6. Configure your screens as required.
If you use the controller blocks from TRANSLINE, then you must ensure
that parameter HMI_DB must be supplied/parameterized with the HMI-
PRO DB (number) of the currently selected station.
If required, delete the original screen.
L DB501.DBB49 //LTLP_HMIProInterfaceData_station_1.net_Index
L 1
==I
= M4.0 //"m_HMI1"
L DB501.DBB49 //LTLP_HMIProInterfaceData_station_1.net_Index
L 2
==I
= M4.1
U M4.0 //"m_HMI1"
SPBN HMI2
L 501 //LTLP_HMIProInterfaceData_station_1
T DB19.DBW128 //"MMC".MMC1_TRANS_DB
SPA screen
HMI2: U M4.2
SPBN screen
L 511
T DB19.DBW128 //"MMC".MMC1_TRANS_DB
Diagram: NOP 0
Fig. 10-9: Softkey/function key number of a screen in the function key screen
TRANSLINE library
The blocks, data types, and example DBs are stored in the TRANSLINE library
under types/copy template in the Graph directory.
11.1 Specifications
In the GRAPH blocks used for the manual control, the setting "Permanent
processing of all interlocks in manual operation" must be activated so that
executability can be accordingly displayed.
The name of the instance of a GRAPH block should not exceed 40 characters in
length because internally and in the parameterization no more than 40 characters
are reserved. Note that the quotation marks at the beginning and end of the name
in the parameterization must be taken into account. This means that only 38
characters are available for the actual instance name.
In the properties of the GRAPH block, under the General tab, you must set version
V4.0.
Parameter description
The block has no parameters.
Fig. 11-7: Read instance name of the GRAPH block when the PLC restarts
0x0000 No error
0x7001 Message: No manual operation
0x0010 Error: GRAPH version not correct (not V4)
Parameterization
instanceName WString[40] The instance name of the GRAPH block should be specified
here. The quotation marks "" should be specified, as the
function GetInstanceName supplies quotation marks.
stepNumber Int Step number of the GRAPH block that must be activated for
the manual function.
activateOffSQ Bool
activateSOn Bool
Operating messages
Operating messages are intended for displaying normal operating states as
information for the operator. Acknowledgment signals are, therefore, not required.
An entry is made in the operating message buffer for incoming and outgoing
messages. The operator panel (HMI device) maintains an up-to-date log of existing
operating messages using the identifiers Operating message arrived and
Operating message gone.
Error messages
Error messages display error states at the machine, which could result in a
machine stoppage. If several errors occur simultaneously, it is important to be able
to distinguish their order of occurrence for troubleshooting purposes. This is
indicated, on one hand, by the order in which they are entered in the error
message buffer and on the other, by the time stamp, which is assigned to each
entry. If the cause of the error has disappeared, the error message is only cleared
if the user has acknowledged the message.
I Block index
I
I.1 Symbolic block names
DB
FB
FC
Siemens AG Corrections
For Publication/Manual:
TRANSLINE Support
P.O. Box 10 60 26 Solutions for Powertrain
Sender Manual
Name: Available at:
DF MC-SIOS Extranet
Edition 2018
Address of your Company/Dept.
If you come across any misprints in this
Street: document, please let us know using this form.
Zip code: ____________ Location: Suggestions for improvements are also
welcome.
Telephone: __________ /
Fax ________ /
Siemens AG
Digital Factory
Motion Control
Postfach 3180
91050 Erlangen
Germany