00192375-01 - 第231页
SIPLACE GEM for S25, HS50 SW Version GEM 502.01 HOST Inter face Manual ©Siemens AG, all rights reserved page 231 of 236 $ ODUPV There ar e no alarm s def ined for SIPLACE $/ , ' $/ & ' $/ 7 ; 'HVFUL…

SIPLACE GEM for S25, HS50 SW Version GEM 502.01
HOST Interface Manual
Page 230 of 236 ©Siemens AG, all rights reserved
Revolver Head 3
CEID Name Description
2310001 Place3Cycle Placement cycle completed on SP-head 3 and
<PLACEINFOREV3> , <PLACEINFOREV3SUB1>
will be updated.
33
2310002 PickUp3Cycle Pick-up cycle completed on SP-head 3 and
<PICKUPINFOREV3> will be updated.
42
2310003 Nozzle3changed <NOZZLECONF3> changed on revolver head 3
(not in single function mode).
35
2310004 RefRunHead3 Head <HEIGHTREV3> reference run complete on
revolver head 3.
37
2310005 NozzleRefRun3 <NOZZLECONF3> length reference run complete
on revolver head 3.
35
2310006 VacRefRun3 <VAKUUMDATAREV3> reference run complete on
revolver head 3.
39
Revolver Head 4
CEID Name Description
2410001 Place4Cycle Placement cycle completed on SP-head 4 and
<PLACEINFOREV4>, <PLACEINFOREV4SUB1>
will be updated.
33
2410002 PickUp4Cycle Pick-up cycle completed on SP-head 4 and
<PICKUPINFOREV4> will be updated.
43
2410003 Nozzle4changed <NOZZLECONF4> changed on revolver head 4
(not in single function mode).
36
2410004 RefRunHead4 Head <HEIGHTREV4> reference run complete on
revolver head 4.
38
2410005 NozzleRefRun4 <NOZZLECONF4> length reference run complete
on revolver head 4.
36
2410006 VacRefRun4 <VAKUUMDATAREV4> reference run complete on
revolver head 4.
40

SIPLACE GEM for S25, HS50 SW Version GEM 502.01
HOST Interface Manual
©Siemens AG, all rights reserved page 231 of 236
$ODUPV
There are no alarms defined for SIPLACE
$/,' $/&' $/7; 'HVFULSWLRQ 21&(,' 2))
&(,'
$/,' Alarm ID
$/&' Alarm Severity Code. The low-order 7-bits of ALCD specifies the severity
code. The high-order bit (bit-8) shows the current alarm state (1=SET,
0=CLEAR).
$/7; Alarm Text. This is the actual string sent the Host in the Alarm Report
(S5F1).
21&(,' This is the Collection Event that is signaled when the alarm state changes
from CLEAR to SET ("going-on").
2))&(,' This is the Collection Event that is signaled when the alarm state changes
from SET WRCLEAR ("going-off").

SIPLACE GEM for S25, HS50 SW Version GEM 502.01
HOST Interface Manual
Page 232 of 236 ©Siemens AG, all rights reserved
3RVVLEOH8VHVRIWKH6,3/$&(*(0,QWHUIDFH
3URFHVV&RQWURO
You can use the SIPLACE GEM interface to check and continuously improve your
production process. To do so, you must monitor critical process parameters. In the event
there are large deviations from the desired value, you can stop the process and make
corrections.
One H[DPSOH3LFNXSUHOLDELOLW\
You can monitor the pickup reliability with the event
CEID 2010016 PickupError.
You will obtain vacuum values from the pickup processes from the Event PickUpxCycle.
You will receive summarizing information about pickup reliability relative to the placement
head and the PCB from the variables GANTRYINFOREVx. With the variables
SEGMENTINFOREVx you will obtain summarizing information relative to nozzles. This
will enable you to pinpoint, for example, inaccurately adjusted feeders or faulty nozzles.
7UDFHDELOLW\
You can collect all data you require to retrace the use of components on the various
PCBs.
If you store this data, you can still ascertain later, e.g., if there are recall actions, which
PCBs were populated with components from a faulty batch.
You can use the component barcode to acquire the batches used. With a few GEM
events you can ascertain where which components were placed:
,GHQWLI\LQJ&RPSRQHQW%DWFKHV
Work with setup check and have the component barcode reported to you via the event
ComponentBCRead (CEID 920002). Store the component barcodes and the
corresponding locations where the feeders were set up.
7UDFLQJWKH,QGLYLGXDO3&%
You can use the event CEID 920001 BCRead to report the PCB barcode. You will then
know the individual PCB. On the basis of the events of the PB conveyor you can ascertain
where the PCB is located. You can monitor the PCB without difficulty in the case of the
S25 because there is only one placement area there. In the case of the HS50 with 2
placement areas, you will have to track the PCB on the basis of the transport messages
and the states of the conveyor belt (e.g., INTERMEDIATECONVEYORSTATE).
&ROOHFWLQJWKH3LFNXS'DWDSHU3&%
The beginning and end of a PCB's placement are reported with the events
PCBreadyProcxConvx. During placement you receive all of the relevant data from the
variables PICKINFOREVx, PLACEINFOREVx and PLACEINFOREVxSUB1. Use this to
ascertain, e.g., the pickup locations, and allocate this data to the current PCB.
/LQNLQJWKH'DWD
Using the pickup location as the basis, you can link the PCB to the current batch.