5.4.
Stop functions including emergency stop
The
e-Brick
, or an
e-Brick
based system, may be ‘stopped’ in three of ways:
Stop method
Initiation
e-Brick
Response
System
Emergency stop
(E-stop)
External system opens
E-stop contact inputs to
master
e-Brick
•
Automatic breaking of
e-Brick
E-stop loop
to deselect all slave lamps
•
Lamps will be switched off instantaneously
•
System cooling correctly controlled
•
System communications will remain
functional allowing quicker restart
Electrical
isolation
Switching off individual
e-Brick
MCB or system
electrical isolator
•
Lamp(s) will be switched off instantaneously
•
If master
e-Brick
is isolated in this way
there will be no system cooling control, refer to
warning below!
•
On restarting, lamps will be deselected by
default and shutters closed automatically
Software
shutdown
HMI
•
Lamps will be switched off instantaneously
•
System cooling correctly controlled
•
System communications will remain
functional allowing quicker restart
Warning!
To avoid lamp damage due to overheating, or potential fire hazard in the web, do not
stop the system by simply isolating the power. It is strongly recommended that power be
maintained to the
e-Brick
when a system E-stop event occurs; this will ensure that the shutters
operate correctly and lamps are properly cooled.
Advice!
Depending on lamp temperature, the stop method, and the duration of the stop, it may
take a few minutes to restart an
e-Brick
system. The embedded control software will only allow
the
e-Brick
to run when all safety interlocks are in place and lamp temperatures are within
acceptable limits.
5.5.
Sequence of operation
For safety reasons, the embedded control software will prevent an
e-Brick
system from running
until all safety interlocks are in place and lamp temperatures are within acceptable limits. Following
installation and commissioning by GEW, the system shall be operated in accordance with the
relevant HMI software manual.
GEW UV
e-Brick
installation and operating manual
32 of 49
