00196806-01_IM_EDM_1.9_EN.pdf - 第46页

Installation Manu al SIPLACE Engine ering Data Manag er (EDM) Version 1 .9 Issue 02/2009 46 ClearObjectSelectionA f terDataTransfer true Data Transfer Manager Specifies whethe r the object selec tion is to be cleared aft…

100%1 / 65
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 02/2011 Edition
45 / 65
objects). If OperatorMayOverride.AllowReject is
enabled, this setting acts as the default value and can
be overwritten for each individual push operation in the
Data Transfer Manager.
AllowDelay true Data Transfer
Manager
Specifies whether the line engineer is allowed to delay
a push. Delaying causes the GUI on the EDM line to be
minimized for a time to that work on the EDM line is not
obstructed.
If OperatorMayOverride.AllowDelay is enabled,
this setting acts as the default value and can be
overwritten for each individual push operation in the
Data Transfer Manager.
OperatorMayOverride.AllowDelay false Data Transfer
Manager
AllowDelay can be overridden in the Data Transfer
Manager.
OperatorMayOverride.AllowReject false Data Transfer
Manager
AllowReject can be overridden in the Data Transfer
Manager.
OperatorMayOverride.ConfirmAtLineServer false Data Transfer
Manager
ConfirmAtLineServer can be overridden in the
Data Transfer Manager.
5.2.4.4 Protection against overwriting current production data
In some cases, it makes sense to suppress the pushing of recipes or boards that are currently being
assembled on the production line. In the initial setting for push mode, the user at the line is requested to
confirm the push and is thus responsible for the decision as to when to import the data. If this dialog box is
not required (e.g. ConfirmAtLineServer is set to „false“), the push would be executed immediately.
The following settings delay import of the data until such time as a new recipe is specified. The fine
settings (EnableLineDataConflictChecks.Board, EnableLineDataConflictChecks.Job,…)
relate to the type of the pushed objects. Dependent data is not taken into consideration (if, for example, a
recipe is being produced that requires setup A, setup A is nevertheless overwritten if a different recipe with
setup A is to be imported).
Setting Default Valid for Explanation
EnableLineDataConflictChecks false Line Enables overwrite protection.
EnableLineDataConflictChecks.Board true Line Protects the board currently being produced.
EnableLineDataConflictChecks.Job false Line Protects the job currently being produced.
EnableLineDataConflictChecks.ProductionSchedule false Line Protects the current production schedule.
EnableLineDataConflictChecks.Recipe true Line Protects the recipe currently being produced.
EnableLineDataConflictChecks.Setup true Line Protects the setup currently being produced.
5.2.4.5 Settings for the data transfer / push mode GUI
5.2.4.5.1 Behavior
Setting Defaul
t
Valid for Explanation
ClearCommentAfterDataTransfer false Data Transfer
Manager
Specifies whether the comment window is to be
cleared after the push operation.
ClearDisplayNameAfterDataTransfer false Data Transfer
Manager
Specifies whether the display name is to be cleared
after the push operation.
ClearLineSelectionAfterDataTransfer false Data Transfer
Manager
Specifies whether the line selection is to be cleared
after the push operation.
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 Issue 02/2009
46
ClearObjectSelectionAfterDataTransfer true Data Transfer
Manager
Specifies whether the object selection is to be cleared
after the push operation.
5.2.4.5.2 Parameters
Setting Default Valid for Explanation
LineDataTransferStatusMonitor.OldEntriesThreshold 30 days Data Transfer
Manager
Specifies the period after which an entry in the
status monitor is classified as "old" in the Data
Transfer Manager (and is therefore removed with
the "Delete old entries" button).
History.MaxiumLength 10 Data Transfer
Manager
Maximum number of history entries in the Data
Transfer Manager.
5.2.5 Configuration of the VDM BLOB functions
To use the VDM BLOB functions, the names of the SPI lines assigned to each Line Server must be entered in
the Line Server's configuration file (see 5.2.3.24 Assigned SPI lines). If this section is left empty, BLOBs are
accepted for all lines.
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 02/2011 Edition
47 / 65
5.3 Configuration of the workflow
The production process design varies greatly from customer to customer, which means the data storage
process also varies. Two aspects in particular stand out in this regard:
• the actual process of data flow – the dynamic part – between the central server (EDM Master Server)
and the local clients (EDM Line Servers), and
• the type and amount of data to be transferred – the static part.
Both parts of the process may differ, though, in customer processes. This section deals with the dynamic part,
the actual control of the flow of data. The configuration of the static part – the application templates – is
discussed in 5.4.1 Application templates.
NOTE:
The workflow only needs to be configured if the default values do not work in your
environment.
5.3.1 Theory …
The production process of the customer is depicted in a workflow using a finite state machine. A finite state
machine is a concept from theoretical computer science. It helps to know a little terminology to understand
this concept.
A finite state machine generally consists of:
• a set of states. In the following, this set is called Q.
• exactly one start state belonging to Q.
• a subset of Q that contains the valid end states.
• a subset of Q that contains the error states.
• a set of Events
1
.
• a set of state transitions that cause a state q
1
to move to state q
2
when a certain event occurs. A
maximum of one transition can be defined for each state/event pair.
5.3.2 … and application
5.3.2.1 Syntax and options
The theory presented in the previous section must now be implemented in a manageable form for actual
use. This is done in the client workflow configuration file (see also 5.2.3.21 Client workflow configuration).
This file is in XML format. The following text deals with the contents of this file and how they relate to the
theory.
1
This set of events is termed the "input alphabet" in theoretical computer science. For those of you who are interested!