an ECU unit is configured and it does not communicate with the controller
althought it is required to communicate.
Alarm output: SHBinCfgErr
Related FW
3.2
Description
The output is closed while there is the SHBinCfgErr alarm present in the alarm list,
i.e. if there is more than one controller on the CAN2 bus, which has configured
the SHBOUT peripherial module with the same index.
Alarm output: SHAinCfgErr
Related FW
3.2
Description
The output is closed while there is the SHAinCfgErr alarm present in the alarm list,
i.e. if there is more than one controller on the CAN2 bus, which has configured
the SHAIN peripherial module with the same index.
Alarm output: ECUDiagBlocked
Related FW
3.2
Description
The output is active when receiving of diagnostic messages from the ECU is
disabled
Alarm output: WrongConfig
Related FW
3.2
This output is closed while there is the WrongConfig alarm present in the alarm
Description
list. The wrong configuration is indicated if the controller configuration contains a
PLC program, which exceeds limits of the current controller hardware. Typically
this situation can occur when a miniCHP archive is used in a controller without
mCHP dongle inserted.
Alarm output: Dongle incomp
Related FW
3.2
Description
This output is closed while there is the Dongle incomp alarm present in the alarm
list. The incompatible dongle is indicated when a function is switched on, which
requires dongle, however the dongle is not inserted or does not contain the
appropriate feature.
Typical situations are:
Inteli NT GeCon-MARINE SPI, SW Version 3.2, ©ComAp – July 2015
IGS-NT-GeCon-MARINE-SPI-3.2.PDF
(ECU diag
= DISABLED).
Power management is enabled and there is not any dongle with "PMS"
feature inserted in the controller.
The controller is in situation, when the load sharing should beeing
performed, however there is not any dongle with "LS" feature inserted in
217
Need help?
Do you have a question about the IG-NT GC and is the answer not in the manual?
Questions and answers