00197458-01_UG_EDM_V2.2_en.pdf - 第82页
EDM V2.2 / U ser Guid e Ausgabe 10/2013 E dition 82 6.2.7.3 User G uid ance o n t he ED M Client These par ameter s specif y how t he various p ush oper ations are pr esente d to the user at the EDM Client. Setting Defau…
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
81
2
. Preserve Missing Blobs. The Vision data information on the EDM Line Server
should be retained. Any change to or deletion of the line or station BLOBs on
the Master is not transferred to the Vision data on the EDM Line Server.
To achieve this, the value "9" must be retained for
xmlImportVisionDataAdvancedAction in the configuration of the EDM
Line Server.
6.2.7 Configuring Push Mode
Push mode provides a large number of settings that allow EDM to be tailored to the needs of the
customer.
6.2.7.1 General Settings
Setting Default Valid
for
Explanation
EnablePushMode false ALL Activates push mode. This setting
must be enabled on all EDM
computers (EDM Master, EDM
Client and EDM Clearing Pool) that
are to participate in push mode.
Table 6-9: General settings
6.2.7.2 Automatic Push in the Clearing Pool
Auto Push can maintain the consistency of the data if a line engineer on an EDM Client makes
changes to an object that are rejected in the Clearing Pool. In this event, the version of the object in
the EDM Master can be automatically transferred to the line. This means that the object on the line
that is invalid from the perspective of the data preparation engineer is replaced by the copy in the
EDM Master.
Setting Default Valid
for
Explanation
ClearingPool.AutomaticPush.Enabled false Clearing
pool
Activates Auto Push at the
Clearing Pool.
ClearingPool.AutomaticPush.
RequireConfirmation
true Clearing
pool
Specifies whether the Clearing
Pool should show a confirmation
dialog box on every Auto Push.
Table 6-10: Settings for Auto Push
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
82
6.2.7.3 User Guidance on the EDM Client
These parameters specify how the various push operations are presented to the user at the EDM
Client.
Setting Default Valid for Explanation
ConfirmAtLineServer true Data
Transfer
Manager
If set to "true", a confirmation
dialog box is displayed on the EDM
line for the push operations to be
imported. Otherwise, the import is
executed immediately.
If OperatorMayOverride.
ConfirmAtLineServer is
enabled, this setting acts as the
default value and can be
overwritten for each individual push
operation in the Data Transfer
Manager.
AllowReject
false Data
Transfer
Manager
Specifies whether the line engineer
is permitted to reject the push
operation (or is forced to import
pushed objects). If
OperatorMayOverride.AllowR
eject 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
certain period of time; the line
engineer will have to handle the
data request when the GUI
reappears after that period.
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.ConfirmAtLine
Server
false Data
Transfer
Manager
ConfirmAtLineServer can be
overridden in the Data Transfer
Manager.
Table 6-11: Settings for user guidance
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
83
6.2.7.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,…) are related to the type of the pushed objects.
Dependent data is not taken into consideration (if, for example, a recipe is being produced that
requires component A, component 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.
Table 6-12: Settings to protect against overwriting
6.2.7.5 Settings for the Data Transfer / Push Mode GUI
Behavior
Setting Default Valid for Explanation
ClearCommentAfterDataTransfer false Data
Transfer
Manager
Specifies whether the comment
text box 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.
ClearObjectSelectionAfter
DataTransfer
true Data
Transfer
Manager
Specifies whether the object
selection is to be cleared after the
push operation.
Table 6-13: Settings for data transfer - behavior