00197202-02_VB_Traceability_3.5_de_en.pdf - 第34页

Fixed Defects 34 SIPLACE Traceability 3.5

Fixed Defects

SIPLACE Traceability 3.5 33

6 Fixed Defects

Fixed defects in other systems

Information about fixed defects in other systems affecting traceability can be found in the relevant soft-

ware version descriptions:

Fixed defects in Traceability

Error number Description

D1-68175811 No connection between Traceability Service and X4 - X4 - SX2.

D1-69390701 DATA_LOST in TraceData data - not all attributes match the produced board

D1-69399201 Missing Linebased TRC Data from Table 2 at F5HM

D1-69721013 Trace 3.3 does not deliver xml from Sirio line.

D1-70144974 Trace 3.3.0.31 SQL Exception Object not set to reference......

D1-71572701 Trace Data Incomplete, many production stops

D1-74527701 Last machine in line has the same MID as previous one in line in case of soft-

ware version 505.

D1-76711601 TraceService cannot connect to Sirio Stations

Fixed Defects

34 SIPLACE Traceability 3.5

Existing Restrictions

Traceability

SIPLACE Traceability 3.5 35

7 Existing Restrictions

7.1 Traceability

▪ The Traceability OIB interface, in the product Traceability 3.4 "OIB Interlocking Interface", will be dis-

continued and will no longer be available in future versions. This interface will be replaced with the

new "OIB Eventing Interface".

▪ Traceability 3.5 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 5.x software version de-

scription can lead to incorrect traceability data.

▪ The following features of SIPLACE Setup Center 5.0 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 since SIPLACE Trace Service 3.3 in the default configuration. For further

information about this, contact your local SIPLACE customer support.

▪ 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:

Station software Single conveyor Synchronous dual convey-

Asynchronous dual convey-

407 / 505 / 605 / 70x 40 40 / 40 40