Small Traceability für Asus - 第38页
2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO 11/2005 Edition 38 2.10 2nd Source 2.10.1 General With this Function it is possible to consult a t able…
SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1
11/2005 Edition
37
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
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
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
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
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
2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO
11/2005 Edition
38
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
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
2
New button to view/change the 2nd-Source-File via Notepad: 2
2
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
2
2
2
SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1
11/2005 Edition
39
– The separator is a space, thus there are no spaces allowed in component names!. It is defined
in the registry under "2ndSourceSeparator"
– The Linecontrol computer must have a directory that the station (User Operator) can unrestric-
tedly access. It is defined in the registry under "2ndSourcePath"
– The directory mentioned above must have a file with the name 2ndSource.txt. It is defined in
the registry under "2ndSourceFilename".
– To avoid a „sharing violation“ it is not allowed to do a barcode verification while a 2ndSource-
File is being created.
2