00192231-09_VD_SSW 407.05_de en - 第14页

Software Version Description, Station Software Version 407.05 07/2008 Edition 5 New Functions 5.1 New Functions in 407.05 Software version 407.05 is based on Version 407.04 SP2 and comprises all the functions and error c…

100%1 / 208
Software Version Description, Station Software Version 407.05 07/2008 Edition
CAUTION !
Following the exchange of GAL and Quartz on the
MVS, the entire machine has to be measured!
For the calibration of the machine, the calibration tool
pocket with integrated machine zero point has to be
installed!
The V24 link from the machine controller to the station
computer needs to be disconnected on both sides if
the predecessor software version used at the machine
is of an earlier release than 404.01.
On no account should the machine be switched off
during the download of the ICOS software to the MVS.
13 of 104
Software Version Description, Station Software Version 407.05 07/2008 Edition
5 New Functions
5.1 New Functions in 407.05
Software version 407.05 is based on Version 407.04 SP2 and comprises all the functions and error
corrections for this version.
The corrected defects are described in chapter 6.
5.1.1 Revision of the Forced Setup Verification
The forced setup verification at the SIPLACE placement machine can be activated via SIPLACE Setup
Center. The forced setup verification monitors the verification status of individual tracks. Non-verified tracks
are disabled to force setup verification.
Forced setup verification is carried out with a connection to the station and requires successful setup
verification before production. This is implemented as follows: once an order or a packaging unit changeover
has been downloaded, the machine deactivates all divisions in which there are packaging units for which no
setup verification data has been received.
This means the line operator needs to successfully verify all the necessary components/packaging units for
the product before production can begin.
A detailed description can be found in the "Installation Manual SIPLACE Setup Center 3.0", item no.
00195642-xx.
Requirements
The forced setup verification requires SIPLACE Pro as of Version 5.0 and SIPLACE Setup Center as of
Version 3.0.
If Splice sensors are used, SIPLACE Pro as of Version 5.2 and SIPLACE Setup Center as of Version 3.0 are
required. Withour Splice sensors SIPLACE Pro as of Version 3.2 and Setup Center as of Version 3.0 are
required.
5.2 New Functions in 407.04 SP2
Software version 407.04 SP2 is based on Version 407.04 SP1 C and comprises all the functions and error
corrections for this version (and includes also the patch "Mobilink").
There are no further new functions in this version.
The corrected defects are described in chapter 6.
14 of 104
Software Version Description, Station Software Version 407.05 07/2008 Edition
5.3 New Functions in 407.04 SP1 C
5.3.1 Synchronization of data provision
Integration of the "Mobilink" patch
In order to avoid data provision problems on a job change, the Setup Center only sends the data to the
station when data preparation has been completed and the new job has been specified by SIPLACE Pro.
The Setup Center and the station are synchronized when a job is specified.
5.4 New Functions in 407.04 SP1
Software version 407.04 SP1 is based on Version 407.04 and comprises all the functions and error
corrections for this version. Version 407.04 SP1 of the software also incorporates the following new features
and changes:
Revised traceability
5.4.1 Revised Traceability
Data provision for the XML files which are generated has been improved and the functionality has been
corrected (see below).
In addition, manual entry of the PCB barcode can be prevented using an activation facility.
Consult your service engineer if you have any questions.
The behaviour of the traceability feature has also been changed. The XML files are only written when the
PCB leaves the station (either in the normal manner or if it is removed by hand). Problems may occur if the
machine is switched off while a PCB is still in the station.
5.4.1.1 Extension to support Version 1.1 or 2.1 of XML
Previously, the PCB barcode was logged in the XML file when the traceability data was output. It was
however not clear how this data was entered in the output (automatically after successful barcode scanning
or by manual entry). Manual entry often resulted in duplicate or missing XML files from a given machine. For
this reason, manual entry of the PCB barcode is now documented in the file using the errorLabel (4096).
15 of 104