00197717-02_VB_Traceability4.1_DE_EN.pdf - 第31页

Existing Restrictions Traceability SIPLACE Traceability 4.1 31 5 5 E x is t in g R e s t r ic t io n s Existing Restrictions 5.1 5 . 1 T r a c e a b ilit y Traceability ▪ The Traceability OIB interface "O IB Interlo…

System Requirements and Software Components

Configuration

30 SIPLACE Traceability 4.1

Existing Restrictions

Traceability

SIPLACE Traceability 4.1 31

5 Existing Restrictions

Existing Restrictions

5.1

5.1 Traceability

Traceability

▪ The Traceability OIB interface "OIB Interlocking Interface", has been discontinued and will no longer

be available in future versions. This interface will be replaced with the new "OIB Eventing Interface".

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

scription can lead to incorrect traceability data.

▪ The following features of SIPLACE Setup Center 7.x 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.

▪ When using dual conveyors, the conveyor lane is unknown if the following requirements are present:

– The line has been configured for station-based traceability

– The traceability information is generated on stations with station software 40x/50x or 60x.

– The job in the LCGUI uses the same setup, recipe or board on the two lanes.

▪ 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 characters 40 characters / 40 charac-

ters

40 characters

From SiplacePro 11.2

and 707.1

255 characters 255 characters / 255 char-

acters

255 characters

Existing Restrictions

Traceability

32 SIPLACE Traceability 4.1

▪ The length of the setup name is limited to 20-50 characters, i.e. only the first 20 to 50 characters will

be taken into account during setup changeovers.

▪ The unique ID for a packaging unit may have a maximum of 40 characters.

▪ If you change the configuration of the Traceability system the SIPLACE line has to be empty. Other-

wise Traceability data may be incomplete.

▪ Station based and line based traceability cannot run simultaneously in the same line.

▪ If a station is part of several lines (SIPLACE Pro configuration), there are the following restrictions

for line based traceability:

– Only one of the lines may be active at the same time.

– If an external PCB barcode reader is allocated to more than one line then the PCB barcodes are

assigned to the line which is active in Trace Service. If there are multiple lines active with the

same external barcode reader, Trace Service will issue an error message. Traceability data can

not be reliably generated in this case.

▪ In case of line based traceability the sequence of the boards may only be changed (e.g. by a pro-

ductivity lift) if there are external PCB barcode readers in front of AND at the end of the line.

▪ The option "Remove unused charges" in the TraceService Monitor requires that you perform forced

setup verification for all the lines for which traceability data are to be generated in "line-based" mode.

If a rear barcode scanner was configured, it should not be positioned directly behind the last

SIPLACE placement machine; there should be a time lag with respect to the last placement (e.g. be-

hind the furnace). Otherwise, Traceability data may be incomplete.

▪ The "Station-based traceability" mode with the "Create one combined Traceability data packet for

each board side" option activated entails the following limitations:

– At least 2 stations must be configured in the respective line.

– Each station in the line must be able to produce traceability data with PCB barcode (either via

PCB barcode scanner or via Whispering option).

– If the PCB label is placed, it must be placed at the first station in the line.

– The "MachineID" attribute is not available in the combined traceability file.

For 407

▪ When using a synchronous dual conveyor, traceability data can only be generated to a limited de-

gree. The restriction is based on the fact that both boards are seen as one panel and that the trace-

ability data is therefore stored in one data package. The board barcode used is always the barcode

read at conveyor 1.

Station software Max. length of setup names

407 20 characters exc. path

505 50 characters exc. path

605 256 characters inc. path

70x 256 characters inc. path

NOTICE

Station and line name

The station name must be unique in the line. The line name must be unique throughout the

traceability system.