Small Traceability für Asus - 第37页

SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (S TA ) on the basis of station software version 505.03 SP 1 11/2005 Edition 37 Deactivated tra cks can be activate d one by one in the "Empty tracks" v…

2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO

11/2005 Edition

2.8 Troubleshooting

Specify new setup (new setup name and different feeder track occupancy) and verify the feeder

again, if there is no identical track. This resets all the data stored at the station. 2

If component verification is deactivated (machine option), production can continue without com-

ponent verification and without traceability data being recorded in the database. 2

If the message "Internal error" appears in the component verification dialog box, the machine must

be restarted. 2

If the same part with a new ReelID is used in a new Setup (new change over table) this is not. 2

2.9 New functions

To verify a feeder track carry out one of the following actions: 2

– Scan a track barcode at the machine ("Setup location“ view or "Empty tracks" view)

– Press the "Comp. verification" button ("Setup location" view).

– Press the "Comp. verification for the entire location" button ("Setup location" view).

In this case the STA software functions exactly as component verification always has. 2

Then a dialog box appears for the corresponding track to allow you to record a container ID (Re-

elId) barcode. 2

This dialog box remains open until an acknowledgement from the database has been received.2

The dialog box closes automatically if the acknowledgement is positive. A suitable error message

is displayed if the acknowledgement is negative. The operator can then either quit the dialog with

"Cancel" or scan in a new barcode. 2

Only positively verified data is written to the TRACE_LOG table. 2

If a barcode is scanned for a track which has not yet been verified, the absolute quantity from the

database is set in the component level indicator. 2

If a new barcode is scanned for a track which has already been verified, the quantity from the da-

tabase is added to the current filling level. 2

The remaining filling level from the old container is added to the new container and the filling level

of the old container is set to 0. The filling level is changed immediately. 2

If the same barcode is scanned again for a track which has already been verified, the filling level

remains unchanged in the component level indicator. 2

SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1

11/2005 Edition

Deactivated tracks can be activated one by one in the "Empty tracks" view. In this case, the soft-

ware checks whether activation is permitted and if necessary sets the track to empty again. Addi-

tional scanning of barcode has no effect. 2

Filling levels are written back after a specified number of PCBs have been completed (can be tog-

gled on and off) for all the relevant tracks (controlled by the setup ("DBUpdateCount")). 2

It is recommended that this value is set to 1 insofar as the database permits the resultant volume

of queries. 2

As a backup measure, the filling levels of the old setup are updated in the database (can be tog-

gled on and off ("DBUpdateWithSetup")). 2

A new function is included in this station Software is called delta setup. If the setup is changed and

the same partnumber is used in the new setup, the “old” part have not to be scanned. 2

The "TimeOut" message indicates that the data query is taking too long. This can have the follo-

wing causes: 2

– Communication with the database has been interrupted

– The reaction time of the SQL server is too long (can also be due to network problems)

– Error in the STA process

The length of the timeout can be changed in the registry. (See the section "Configuration "Dlg-

TimeOut"") 2

7 different error situations are distinguished: 2

– no connection to the database (“no database connection”)

– error on a database operation (“database error”)

– no data found in the database (“no data found”)

– component name from the database does not match component name in the setup (“wrong

component”)

– component name from the barcode label does not match component name in the setup (“com-

ponentlabel reelId mismatch”)

– invalid container size

The error message texts can be configured at the registry to a limited extent. 2

2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO

11/2005 Edition

2.10 2nd Source

2.10.1 General

With this Function it is possible to consult a table of replacement components during a component-

barcode verification. Thus, a component with another name can be verified on-the-fly without

changing the set-up on the programming system. 2

If the barcode cannot be verified, this new feature searches for the component name, which is

setup for the track to be verified, in a 2ndSource file. If the component name is found, it is compa-

red to the name acquired from the barcode scan. 2

If a match is found, the component is declared to be positively verified. 2

If no match is found or if there is no 2ndSource file available, the component is declared as being

negatively verified. 2

A new button has been introduced in the set-up overview that allows the corresponding

2ndSource file to be shown. It is recommended to check if the 2ndSource file is accessible from

the station using this function. 2

New button to view/change the 2nd-Source-File via Notepad: 2

2.10.2 Requirements

The 2ndSource-File must have the following format: 2

ComponentFromSetup1 2ndSourceComponent1 (e.g. 11-033410400 11-033410401) 2

ComponentFromSetup1 2ndSourceComponent2 (e.g. 11-033410400 11-033410402) 2

ComponentFromSetup1 2ndSourceComponent3 (e.g. 11-033410400 11-033410403) 2

ComponentFromSetup2 2ndSourceComponent4 (e.g. 11-033410404 11-033410405) 2