IGS-NT-2.2-New Features
IGS-NT-2.2-New Features
2 Page 1 of 3
Archives
IG-NT Archives IG-NT Archives IS-NT Archives
IG-SPTM-2.2.ant IG-SPTM-mCHP-2.2.ant IS-SPTM-2.2.ant
IG-SPI-2.2.ant IG-SPI-mCHP-2.2.ant IS-SPI-2.2.ant
IG-MINT-2.2.ant IG-MINT-mCHP-2.2.ant IS-MINT-2.2.ant
IG-COMBI-2.2.ant IG-COMBI-mCHP-2.2.ant IS-COMBI-2.2.ant
IG-COX-2.2.ant IG-COX-mCHP-2.2.ant IS-COX-2.2.ant
Documentation
PDF files Description
IGS-NT-SPTM-2.2.pdf Manual for IG/IS-NT Single Parallel to Mains application
IGS-NT-SPI-2.2.pdf Manual for IG/IS-NT Single Prime Island application
IGS-NT-MINT-2.2.pdf Manual for IG/IS-NT Multiple INTernal application
IGS-NT-COX-2.2.pdf Manual for IG/IS-NT in COoperation with an eXternal system
IGS-NT-COMBI-2.2.pdf Manual for IG/IS-NT in COMBIned applications SPtM, SPI
and MINT
IGS-NT-2.2-Application guide.pdf Application guide for IG/IS-NT
IGS-NT-2.2-Installation guide.pdf Installation guide for IG/IS-NT
IGS-NT-2.0-Operator guide.pdf Operator guide for IG/IS-NT
InteliCommunicationGuide – December Communication guide for IG/IS-NT, ID and Il controllers
07.pdf
Ap
om s.r.
C
o.
alit
Qu
en
list, the controller is in Ready state and Alarm LED doesn't blink. But gen-set start is still blocked
until AMF condition occurs.
• Setpoints for communication setup were moved from Basic settings group to new Comms
settings group.
• Added setpoint Comms settings:LB/UART Log [DISABLED / ENABLED] which optionally disables
"Terminal" history records.
• Number of SHAIN and SHAOUT modules increased to 2.
• Number of inputs/outputs from/to ECU is selectable between Standard and Large which means 16
binary inputs and outputs, 16 analog inputs and 4 analog outputs for Standard selection and 32
binary inputs and outputs, 32 analog inputs and 8 analog outputs for Large selection.
• If Mains is OK, MCB feedback is active and the controller shows "Wrn MCB fail" alarm due to some
previous difference between MCB control signal and feedback, the controller will accept closed
MCB feedback after Fault reset and activate MCB close/open output.
• During Mains fail the controller regulation outputs for gen-set speed and voltage regulation will stay
at their last values and not follow the decreasing mains voltage and frequency.
• Names of binary outputs FaultButnEcho and HornButnEcho changed to FltResButnEcho and
HrnResButnEcho.
• Added setpoint Act. calls/SMS:Acall+SMS lang which enables to select language of active call
messages correspondingly to the language configuration table in GenConfig.
• Default password protection of all setpoints set to level 0 (no protection).
• For analog inputs added calibration offset in configuration (see GenConfig manual for details).
• Improved support of CDMA modems (delay for initialization).
• Added binary input ECUComFailBlck which blocks evaluation of ECU communication failure and
corresponding Fls alarms on analog inputs from ECU.
• Currently forced setpoints are marked with F when browsing through the setpoints from the
controller panel.
• Binary outputs that provide some functionality upon their configuration (like ECU PwrRelay) do not
have to be configured to physical outputs anymore but they can just be configured to some PLC
output.
• IG-NT controller allows to switch only among those languages that are supported (e.g. Chinese is
not shown in the list if the controller doesn't have GC option and chinese font uploaded).
• Added PT100 sensor definition for analog inputs on the controller.
• SMS messages sending possible in Russian language.
• FastEdit access time is shortened to 2 seconds after pressing Enter button.
• ECU LINK option is available also for the second port - in RS232(2) mode setpoint. It means it is
possible to use the RS485(2) port on IS-NT and IG-EEC/NTC controllers to connect to e.g.
Waukesha ESM or Cummins GCS.
• Default name of user U0 changed to Administrator.
Repairs
• Forcing nonzero value to Sync/Load ctrl:Phase window which had previously 0 value didn't
release protection against closing of GCB/MCB.
• If Sync/Load ctrl:Freq reg loop was set to ALL THE TIME generator voltage and engine speed
were regulated already during Engine params:Min stab time although the control loops should
have been activated only after this time had elapsed.
• If gen-set was running parallel and during "Wait Stop" the Slow stop protection was deactivated
and confirmed a GCB open timer started to count down. In AUT mode the gen-set kept running
loaded but in MAN mode GCB was opened.
• Sync/Load ctrl:ManualFuseSync setpoint used to have dimension seconds although it has only
values ENABLED/DISABLED.
• Values REG16/REG32 were not updated correctly when some of the controllers were switched off.
Ap
om s.r.
C
o.
alit
Qu
en
• If Mains protect:Mains V del was set to very short time like 0,01 - 0,06s and very short Mains fail
occured, the controller opened GCB but started to synchronize back immediately, i.e. Mains ret del
was not applied.
• If Date or Time were entered into history record all following data were not displayed correctly.
• Screens modified to look correctly also with Chinese texts.
• If both binary inputs GCB feedback and GCB fdb neg were configured, GCB was closed (GCB
feedback active), GCB fdb neg was not active and then activated, the controller didn't wait for 500
ms and issued immediately "Stp GCB fail".
• If the controller was switched to Emergency manual mode and GCB was closed at the moment
when the controller was switched on, an alarm "Stp GCB fail" was issued although in Emergency
manual this state should have been accepted.
• In SPI application there were binary outputs MCB close/open, MCB ON coil, MCB OFF coil a MCB
UV coil available with no function.
• The controller didn't react on pressing the Stop button in SPI application and SEM mode.
• It was not possible to download configuration via RS-485(1) port. Monitoring and change of
setpoints worked without problems.
• MINT application - during WaitToStop it was not possible to open GCB using GCB button in MAN
mode.
• Fault acknowledgement for ECU using DM3/DM11 frames was previously not done according to
the standard.
• If Basic settings:RS232(1) mode was set to ECU LINK and the controller was switched off and on
again, the setpoint changed back to DIRECT.
• After configuring the protections on binary inputs from ECU, these were not activated. To solve the
problem it was possible to use VPIO module and configure protections on it's inputs.
• After the controller switched from Emergency manual mode to normal operation the Fuel solenoid
output was not activated.
• CtrlHBeat FD binary output was activated for a while after the controller was powered up so it
wrongly indicated that the controller was not in operation.
• PLC functions Force history and Force protection were not activated after start up of the controller
although the conditions were fulfilled.
Ap
om s.r.
C
o.
alit
Qu
en