Small Traceability für Asus.pdf - 第35页
SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (S TA ) on the basis of station software version 505.03 SP 1 11/2005 Edition 35 2.7.3.2 Configuration for Second Source The appropriate entr ies have to be adjust…
2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO
11/2005 Edition
34
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\Msg\2] 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\Msg\3] 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\Msg\4] 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\Msg\5] 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\Msg\6] 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\Msg\7] 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\TraceClient] 2
2
2
"Message"="database error"
@="STA_DB_ERROR"
"Message"="no data found"
@="STA_NO_DB_DATA_FOUND"
@="STA_WRONG_COMPONENT"
"Message"="wrong component"
"Message"="componentlabel reelId mismatch"
@="STA_WRONG_COMPLABEL"
"Message"="invalid container size"
@="STA_WRONG_SIZE"
"Message"="internal error"
@="STA_INTERNAL_ERROR"
"NoScan"=dword:00000001
Values: 0 or 1 ( 0 = inactive, 1 = active, default =1)
When active, deactivated tracks can be activated by clicking a button in the "Empty tracks" list
even when component verification is active. If activation is not permitted, for example if the filling
level falls too low, the corresponding track is deactivated again.
SOKO 2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1
11/2005 Edition
35
2.7.3.2 Configuration for Second Source
The appropriate entries have to be adjusted to the circumstances on each station individually. 2
2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA\2ndSource] 2
2
Additional scope of services 2
Because the station name is not available on the station when it is connected to SiplacePro, it can
now be written in the registry. 2
[HKEY_LOCAL_MACHINE\SOFTWARE\Siemens SIPLACE\Traceability\STA] 2
The computer name will be used if this entry remains empty. 2
2
"2ndSource"=dword:00000001
2ndSourceAddon 1 = active --> 0 = inactive --> Default is active
"2ndSourcePath"="\\Linecontrol\2ndSource"
Linecontrol is equivalent to the Linecontrol computer name.
Path for the directory on the Linecontrol computer.
This must be adjusted for each station. 2
"2ndSourceFilename"="2ndSource.txt"
File name of the 2ndSource-File --> Can be adjusted.
"2ndSourceSeparator"=" "
Space between 2 component names --> Default is a space
"StationNameReg"=" --> Has to be adjusted for every station.
2 Retrofit instructions SOKO Small Traceability ASUS (STA) on the basis of station software version 505.03 SP 1 SOKO
11/2005 Edition
36
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
2