InteliLite
NT
AMF26-P, SW version 2.4, ©ComAp – January 2016 96
AMF26-P-2.4 Reference Guide.pdf
Man Operations
This group doesn’t contain typical setpoints. The two items in this group are commands.
EF Prot Test
This command is normally in OFF state. When you set this command to ON state Earth Fault
protection test is performed and command state is automatically returned to OFF state.
This test can be performed anytime (even in OFF mode), when Emergency Man mode is not active.
When the test is performed Earth Fault Sd protection, BREAKER TRIP output and Wrn EF Prot Test
alarm message are activated and stay active unless FAULT RESET is pressed.
Hint:
When Sd Override is active and EF Prot Test is set to ON, Sd Earth Fault is recorded into the history
file and appears on controller display, but gen-set remains running and Breaker Trip output is NOT
activated. If you deactivate Sd Override before Sd Earth Fault is acknowledged by pressing FAULT
RESET, then gen-set is immediately stopped and Breaker Trip output is activated.
For more details about Sd Override see Sd Override description.
EF Prot Test command may be also executed using controller buttons combination (see more in
chapter Earth Fault Protection Test) or by binary input EF PROT TEST.
RestoreDefault
This command works the same way as the previous one. Normally is in OFF state. When you want to
execute this command you have to change its value from OFF state either to SET1 or to SET2. There
are two sets of default parameters. Once you choose one SET controller setpoints are restored to
respective default setting and command state is automatically returned to OFF state.
Most of the setpoints are restored to default, but not all of them. There are following exceptions.
x GenSet name
x ControllerMode
x ControllerAddress
x COM1 mode
x COM2 mode
x ModemIniString
x ModbusComSpeed
x Maintenance
x SummerTimeMode
x Time
x Date
Hint:
These are the same setpoints which are not overwritten during configuration download.
In this particular cases it doesn’t make sense to change the setpoints because of following reasons. GenSet
name should be unique name, ControllerMode should stay the same to avoid any unwanted action,
communication setting is usually changed according to the particular application and returning to the default
setting would mostly cause lost of communication, time and date are usually up-to-date and it would set it
out-of-date, Maintenance setpoint shouldn’t be obviously changed at all and even if it should be judged
seriously and changed separately and not as a part of restore to default command.
To Next Page
Loading...
