00196784-02_VD_Traceability_3.3_DE_EN.pdf - 第40页

Fixed Defects 40 SIPLACE Traceability 3.3

Fixed Defects

SIPLACE Traceability 3.3 39

6 Fixed Defects

Fixed defects in other systems

Information about fixed defects in other systems regarding traceability can be found in the following sta-

tion software version descriptions:

▪ Software Version Description Station Software 705.04

▪ Software Version Description Setup Center 4.2

Fixed defects in Traceability

The following defects have been fixed compared to Traceability 3.2.

Error Number Description

D1-63433212 Invalid format: Not supported version of tracefile

F1-61688201 Error while deserializing message" / Traceability OIB Interface

F1-61688217 TraceService ErrorReporter uses wrong installation folder

F1-62674501 Trace Monitor treats job-related Trace data incorrectly

F1-62790401 Trace Monitor shows bad headlines in English

F1-62917801 Add line: the lines shown are not sorted

F1-63003019 No connection to station if faulty proxy configuration

F1-63003035 Synchronization SSI not possible

F1-63144807 Version not given for Trace Monitor

F1-63342332 Trace Service produces inconsistent Trace XML file

F1-63600101 Connection to SC-DB failed, error details not shown and also not in LOG

F1-63600517 faulty log messages if rear barcode scan missing (LBTRC)

F1-63958501 'TypeName' should be filled with component name.

Fixed Defects

40 SIPLACE Traceability 3.3

Existing Restrictions

Traceability

SIPLACE Traceability 3.3 41

7 Existing Restrictions

7.1 Traceability

▪ SIPLACE Trace Host is no longer part of the Traceability 3.3 product CD. The database option is

now made available via the SIPLACE Trace Service and can be configured with the Trace Service

Manager.

▪ SIPLACE Trace Service 3.3 supports SIPLACE Trace Host 3.2. This support could be removed in

future versions of SIPLACE Trace Service.

▪ Traceability 3.3 does not support archiving. We recommend that you periodically create a new data-

base and manually archive older versions of Trace database. The Trace Service Manager has a

range of database operations for backing up a non-productive (to be archived) database in the file

system and to then delete this on the SQL server.

▪ Nonobservance of the restrictions specified in the SIPLACE Setup Center 4.2 software version de-

scription can lead to incorrect traceability data.

▪ The following features of SIPLACE Setup Center 4.2 are supported in station based traceability

mode only:

– Alternative Components

– Random Setup on Feeder Tables

▪ The component level indicator in connection with setup verification should always be run with acti-

vated stop thresholds.

▪ When downloading a new setup in line-based traceability, the conveyors must be empty. If this is not

the case, the traceability data may be incorrect.

▪ Line-based traceability does not support station-wise downloads.

▪ Station software version 408 is not supported.

▪ If a track is not fitted with splice detection, the reliability of the traceability data depends on the ac-

curacy of the component levels. The packaging unit change is therefore logged according to the re-

spective component level.

▪ The logging of detected splice points for X feeders (so-called "Splice Events") in the traceability XML

files is no longer performed by SIPLACE Trace Service 3.3 in its default configuration. Customers

who have connected their target system (e.g. "MES") via the XML file interface to traceability (and

not via the database interface), and who evaluate splice events in their application, will need to man-

ually reactivate this data generation via a button in the "ApplicationConfig.xml" - Trace Service file.

For further information about this, contact your local customer support. We reserve the right to no

longer provide the generation of splice data within traceability data in future releases.

▪ The renaming or moving of lines within the programming system "Siplace Pro Desktop" during pro-

duction operations is not supported. To avoid data loss and/or faulty data, the following procedures

should be followed for renaming or moving the Siplace Pro line

name:

– All conveyor lanes in the line must be run empty

– After this, rename the line on the SIPLACE Pro desktop

– Configure the new line name in Setup Center (delete old line, add new one)

– Configure the new line name in Trace Service (delete old line, add new one, apply configuration)

– The production job to be produced needs to be reconfigured at the line, using the SIPLACE Pro

LineControl function.

▪ Traceability data of bulk case feeders, linear feeders and LED feeders can only be used if the oper-

ator makes sure that the feeder is completely empty before each refill.

▪ The following maximum lengths (characters) for the PCB barcode are available if the PCB barcode

is read in the SIPLACE machine: