InteliMains
NT
, SW version 3.2.0
InteliMains-NT-MCB-MGCB-3.2.0-Reference Guide.pdf, ©ComAp – April 2015
Transition closing -> opening (opening command is issued during closing pulse) – Left
Transition opening -> closing (closing command is issued during opening pulse) – Right
0
1
0
1
0
1
0
1
0
1
0
1
CB UV coil
CB ON coil
CB OFF coil
CB fdb
CB fdb neg
0
1
CB status
<2s
2s
CB close/open
0
1
0
1
0
1
0
1
0
1
0
1
0
1
2s
2s
1s
BO/BI
Other CB fail reasons:
When the BO CB close/open is in steady state and CB feedback is changed, the CB fail is detected
immediately (no delay).
0
1
0
1
0
1
0
1
0
1
0
1
CB fdb
CB close/open
CB fail
BO/BI
ON pulse is shortened/interrupted
and replaced by UV and OFF pulse
In this moment, the
reason for closing the CB
is activated again (e.g.
Remote Start/Stop is
activated).
Minimum 1s delay after
UV coil is switched on
is needed before CB
can be closed
OFF and UV pulses are
always activated for the full
time (2s). Manual control (=
CB button) is deactivated
during opening pulse.
Further behavior of UV output depends on the system status.
In case of transition to cooling stays off, if the Cb was opened
manually and the engine keeps running, it activates again
after timeout elapses.
NOTE:
This is not valid for MCB. MCB fail
is not detected in this case.
This is because there can be
additional device which can open
the MCB if one of its protections is
triggered. If this configuration is
used, binary input on the
controller should be connected to
the additional device and
configured to Mains Protect with
according delay for proper
function. Otherwise MCB opens
and the controller accepts this
and no alarm is issued.
Alarm detection is immediate
To Next Page
Loading...
Need help?
General