00197691-04_VD_EDM_3.3_DE_EN.pdf - 第9页
EDM 3.3 / Version Des cr iption Ausgabe 05/2016 Edition 9 4 Features of SIPLACE EDM V ersion 3. 3 If EDM is used, the 3. 3 version is required f or SIPLACE Pro 1 3. 1 . All features of previou s SIPLACE EDM versions are …
EDM 3.3 / Version Description Ausgabe 05/2016 Edition
8
3 Installation and Configuration
The installation instructions and some basic configuration settings can be found in the EDM
Installation Manual, item no. [00197692-xx].
Detailed configuration instructions can be found in the EDM User Manual, item no. [00197693-xx].
EDM 3.3 / Version Description Ausgabe 05/2016 Edition
9
4 Features of SIPLACE EDM Version 3.3
If EDM is used, the 3.3 version is required for SIPLACE Pro 13.1. All features of previous SIPLACE
EDM versions are contained in EDM Version 3.3.
EDM 3.3 / Version Description Ausgabe 05/2016 Edition
10
5 Restrictions
The following restrictions apply to EDM:
● Sometimes, the SIPLACE Pro notification system displays superfluous comment windows. If
this occurs repeatedly, the filter configuration should be adjusted.
● When transferring data from the Master Server to the Line Server to an empty database, you
might have to import the system fiducials 250-252 manually using EDM. If the system fiducials
are not imported before the download is performed, the download will fail.
● A license is required on the Line Server and Master Server. This license must be imported into
the SIPLACE License Manager before installing EDM. If the license is missing, the EDM
Service will not start and the EDM Tool will display an error message.
● If Auto Push is enabled, a push data package is created automatically by the Clearing Pool
and sent to the line if changes are rejected. This is valid for completely rejected changes only,
not for changes that were partly rejected with the Extended Different Editor.
● Extended Difference Editor:
– If you assign a new feeder to a component or to a component shape, the feeder with all its
individual attributes is marked correctly as changed (red) in the Difference Editor. The
button to accept one attribute is already enabled, but the use of the button has
no effect. To accept the feeder with all its individual attributes, first click the feeder name
and then the button.
Alternatively you can click the button to accept all.
– The component barcode filter is only visible in the Difference Editor if you double-click the
icon next to the barcode name (do not double-click the barcode name itself!). The
differences between the both components are only visible in this way.
– If you change a lead group of a component shape, the changes are not displayed correctly
in the Difference Editor:
– If you change only one individual attribute, the whole lead group is marked as changed
(red) - not only this individual property.
– The Difference Editor cannot detect the correlation between the original lead group and
the changed lead group. The original lead group is marked in red and does not find a
counterpart in the changed lead group (right column). The changed lead group is listed
as a new group. This group does not find a counterpart in the original lead group (left
column) either.
– To correct this bug, you must click the button to accept all changes. Do
not use the button to accept only one of the lead groups. In this case, an
additional invalid lead group exists in the component shape.
– For technical reasons, it is not possible to merge fiducial MC and component shape LCU
numbers with the Extended Difference Editor.
● The Do not transfer optimization results option only describes the head steps generated by
the optimizer or the feasibility test at the Line Control GUI. If this option is activated, the
optimized setup will still be transferred. If, on the other hand, this option is not activated, ALL
data, including the optimized setup and head step data, will be transferred.