Small Traceability für Asus - 第30页
2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO 11/2005 Edition 30 2.6 Requirement s – S ta tion software 505.03 SP1 must have been installed succes sf…
SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1
11/2005 Edition
29
These are the contents: 2
2
The database interface can be configured to a limited extent. For details, see the section on Con-
figuration. 2
2
2
2
2
PCBID “TIMESTAMP” by default
RID the scanned ReelId (without prefix)
MPROG
Panel name on Conv1# Panel name on Conv2,
only one panel name if both are the same
QTY Container size
LOC Table_no#Track_no#Division#Level#Tower
TRACE_STATION Line_name#Station_name
2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO
11/2005 Edition
30
2.6 Requirements
– Station software 505.03 SP1 must have been installed successfully and traceability 505.03
SP1 must be active.
– A SIPLACE machine of the type:
SIPLACE HS-50,
SIPLACE HS-50+
SIPLACE HS-60
and SIPLACE HF-Serie.
– Other requirements are described in the manual and the version description for Traceability
505.03 SP 1.
: Do not attempt to install the SOKO on a different software version.
The machine will not start up and you will have to deinstall the SOKO.
2.7 Configuration
2.7.1 Basics at the Programming system
On the programming system, the component verification flag must be set for every component
and the feeder pitch (required for the component level indicator threshold value "Remaining
length in mm") must be entered correctly. 2
Component verification and the Siemens wired hand scanner must be active on the machine. 2
2.7.2 Basics at the Station
Component verification must be active. 2
SIPLACE traceability should be inactive, but the item "Reread barcode if previous setup is identi-
cal" must be inactive. 2
The appropriate threshold values must have been set in the component level indicator. 2
2
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
31
2.7.3 Configuration on the station
2.7.3.1 Configuration for STA
Configuration is carried out in the Registry key only. 2
A basic configuration is entered during installation. 2
The keys can be edited by the program Regedit (Start / Run / Regedit). 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA] 2
"VerifySize"=dword:00000001
Values: 0 or 1 ( 0 = inactive, 1 = active, default =1)
When active, the container size value from the database is checked. An error message
is issued if the container size is invalid.
"VerifyComponent"=dword:00000001
Values: 0 or 1 ( 0 = inactive, 1 = active, default =1)
When active, the component name from the database is compared with the component
name from the setup. An error message is issued if the names do not match.
"VerifyComponentFilter"=dword:00000000
Values: 0 or 1 ( 0 = inactive, 1 = active, default =0)
When active, the component name from the database is compared with the filter
barcodes from the programming system. An error message is issued if the names do
not match.
"PrefixReelId"="R-,R,(R)"
Prefixes are removed from the scanned barcode for further processing.
Prefixes are entered in the registry separated by commas. A specific sequence must be
observed, as the list is processed from front to back.
Example:
R-,R
The prefix R must follow the prefix R-, since in the case of a prefix in the form R-xxxxx,
the prefix R- is removed, and xxxxx remains. If R were at the start of the list, the R would
be removed and –xxxxx would remain.
"BcReelId"=dword:00000001
Values: 0 or 1 ( 0 = inactive, 1 = active, default = 1)
"useSMV"=dword:00000001
Values: 0 or 1 ( 0 = inactive, 1 = active, default =1)
When active, the positively verified data is written to the SMV interface.
The SMV interface is a component of SIPLACE traceability.
"useDB"=dword:00000001
Values: 0 or 1 ( 0 = inactive, 1 = active, default = 1)
When active, the container size and the component name are requested from the
database on the basis of the ID and further processed.