Frequently Asked Questions

Each ComAp device usually allows for multiple ways of connection. The simplest one supported by majority of our devices is RS232 (serial) connection. For this you need an RS232 cable (null modem) and if your PC is not equipped with RS232 port you need a USB<->RS232 converter.

Becoming prevalent in the recent years is USB connection. Almost all ComAp devices support connection using simple USB A<->B cable (printer cable) for easy configuration. Some devices can be powered from the USB port for programming to allow easy configuration right on your desk.

Other connection types: Internet connection (LAN, GPRS, 3G, 4G), Modbus RTU, Modbus TCP, SNMP, AirGate, Modem.

Note that some connection types would require you to use a communication module (plug-in) or communication bridge (external device). Not all types of connection are possible on each device. You can find all details related to this topic in your device's Comprehensive guide or Communication guide.

All ComAp devices come with a software package you can download for free from our website. This package typically contains software tools for configuration, monitoring, commissioning and the latest controller firmware. You can download each tool separately.

Brief overview:

• NanoEdit - Configuration of InteliNano NT and InteliDrive Nano.
• LiteEdit - Monitoring and configuration of InteliLite NT, InteliCompact NT, MainsCompact NT, InteliATS NT, InteliDrive Lite/IPU/IPC series.
• LiteEdit 2015 - Monitoring and configuration of InteliLite.
• InteliMonitor - Monitoring of InteliLite NT, InteliCompact NT, MainsCompact NT, InteliDrive Lite, InteliDrive, InteliGen NT, InteliSys NT, InteliMains NT. Contains SCADA editor to design your own monitoring and control interface.
• GenConfig - Configuration of InteliGen NT, InteliSys NT, InteliMains NT.
• DriveConfig - Configuration of InteliDrive DCU Industrial and InteliDrive DCU Marine controllers.
• WinScope - Tool for real time data monitoring and capture. Highly recommended for commissioning and troubleshooting.

You can download the latest firmware package on the webpage of the device. You can easily navigate there through the Products section or just use the Search function. If you cannot find the firmware on the website or if you require different than the offered version do not hesitate to contact our support team.

The firmware upgrade itself is easy to perform. You need the appropriate configuration software and a connection to the controller (preferably direct connection). Prior to initiating the update process we strongly recommend you to store complete backup of your device.
It usually consists of several steps:

• Create controller back up.
• Update the device firmware. It will contain default Configuration Archive and default Application.
• Change the Application to required type (by programming appropriate default archive to the controller).
• Use the Import Configuration Wizard to restore your previous configuration. In some cases manual interventions might be needed during this step.
• Optional: Update the connected display firmware or device communication module firmware.

Should you be unsuccessful in programming the new version the rollback procedure is to install previous firmware version and use your back up to restore the controller to original state before a firmware upgrade was attempted.

ComAp world is full of abbreviations but once you get basic understanding of their meaning you will find them useful when reading the documentation or communicating with us.

The list of abbreviations which will help you understand them is available for download on this website.

If you forgot your controller password it can be decoded. You will need the following information about your device: 1.) The device serial number. 2.) The "password decode" number. Both numbers can be obtained through the monitoring software relevant to the device. You can also show these numbers on your device's display. Typically this requires a sequence or combination of buttons to be pressed. Details can be found typically in the device Operator guide.

Once you have these numbers, please contact your ComAp distributor and they will help you get your password back.

Yes, where applicable, ComAp devices are capable of communication with electronic engine control units. Typically you connect the ECU directly to the controller using CAN bus. If the ECU does not support J1939 communication protocol you need to use some communication interface either on ECU side (such as SAM CCB2 or SmartConnect modules) or on ComAp side using the I-CB communication bridge.

The communication is typically bi-directional so we support reading of values from ECU as well as sending commands to the ECU (Start, Stop, …) and controlling the engine RPM.

For details including physical connection, configuration steps and troubleshooting help please consult the Electronic Engines Support Guide available on this website.

Usually connecting to the controller over the internet is straightforward and works out of the box. Should you face any difficulties in getting this to work please follow these steps.

• Make sure you have the latest firmware in the controller itself but also in all the communication modules (plug-in, built-in or external).
• Ensure the communication interface is configured correctly. This usually has two parts, one being the controller setpoints (Comms settings) the other being the communication interface configuration. This is typically done using web interface (IB-Lite or IB-COM) - just connect to http://<controller-ip-address>/sp_index.htm using your favourite web browser. InternetBridge NT requires a software tool called IBNTConfig and an USB A<->B cable for configuration. This way you can also enable MODBUS, SNMP etc.
• Make sure there is no firewall blocking your connection. Consult your IT specialist or ISP if not sure. If you use a firewall make sure the following ports are open for communication:
  • The device must be able to send data to the AirGate server at UDP port 6127 and TCP port 23. The TCP port can be changed in the module setup to 21 if needed.
  • TCP port 44445 is required for WebSupervisor connection.
  • Port 80 is used for accessing the communication module web interface.
  • Port 502 is used for Modbus TCP communication (enabled by default).
  • Port 161 is used for SNMP (needs to be enabled).

Synchronizing genset to mains (or multiple gensets together) is a procedure which requires the following conditions to be met before you connect the two electrical systems together:

• Matching voltage in all phases of both systems.
• Matching frequency of both systems.
• 0° phase angle between both systems. (Or as close to 0° as possible.)
• Matching sense of rotation of both systems.

The last condition is predetermined by wiring and needs to be checked prior to commissioning, the rest can be controlled by ComAp device. In order to do so you need to interface the generator AVR (Automatic Voltage Regulator) and the engine Speed Governor. ComAp controllers designed for paralleling operations typically have outputs designed for this connection. Thanks to this we are able to control the generator voltage and the engine speed (and subsequently phase angle).

The procedure of configuring the speed and voltage regulation is described in the relevant documentation, typically the Installation guide or Global guide. The same document also contains the list of supported AVRs and Speed Governors including the wiring and configuration setpoints.

The C stands for Communications. The NTC version contains built-in communication interface to provide additional capabilities such as USB port for direct connection and configuration, Ethernet port for Internet connection and integration into SCADA systems using Modbus TCP or SNMP and an additional RS485 port typically used for MODBUS RTU connection.

Yes, the controller application (single genset, multiple gensets, island operation, parallel to mains operation) can be changed using the controller configuration software. For InteliGen NT this tool is named GenConfig. Here you can select from multiple default Configuration Archives to achieve the desired operation. The biggest differences between various applications are typically in the way site breakers are controlled (MCB, GCB, MGCB) and also what protections are included (you do not need Mains protection when running in Island mode).

If you are not sure which Application is the right one for you consult the Application guide which contains wiring diagrams, descriptions of required controller inputs and outputs and hints on how to configure the setpoints.

AirGate is internet connection related service. AirGate can act like a middle man if you want to connect remotely from your PC but your controller does not have public static IP address or is behind a NAT or a firewall. You just need to make sure the device can access internet. The controller then registers itself automatically on the AirGate server and this server assigns the controller unique ID, so called AirGate ID. Using this AirGate ID you are then able to connect to your controller from anywhere in the world. Your PC will simply connect automatically to the AirGate server, the server knows the current IP address of the controller and opens a communication channel for you.

The controller firmware does not usually break by itself however it can be damaged during controller programming, typically if power is lost during the process. If there does not seem to be a hardware issue with the controller there is an option to restore the controller using so called Boot Jumper programming. This can be described as a sequence of steps you need to perform to allow the configuration tool to write new firmware into the device.

The steps typically are:

• Physically connect the controller to your PC.
• Power the controller on and initiate connection and firmware programming from the software tool menu.
• The software will ask you to switch the device off, close the Boot Jumper and switch the device back on.
• The programming will then proceed and you will receive further instructions during the process.

The boot jumper can be found either on the communication module (where plug-in modules are used) or on the device itself, typically under a rubber grommet, next to the dongle slot.

You can export the list of MODBUS communication objects directly from the controller. In order to do this you need to connect to the controller using the appropriate software (or use an offline archive).

LiteEdit: When you are connected to the controller or have its archive open in LiteEdit please click on: Controller -> Generate Cfg Image -> Generate Cfg Image (Modbus registers - used)...

GenConfig: When you are connected to the controller or have its archive open in GenConfig please click on: File -> Generate Cfg Image -> Generate Cfg Image (Modbus registers - used)…

In order to get SNMP MIB table just replace the last part with "Generate SNMP MIB table…"

This way you will get an exact list of registers which is based on the actual controller configuration.

For further reference please look into the Communication Guide which describes all MODBUS related details.

Vast majority of all issues related to CAN bus come from incorrect wiring. Please ensure the following requirements are met:

• Usage of correct cable - recommended is shielded CAN bus cable.
• The bus topology needs to be strictly linear, no branching, no "star" topology.
• The CAN bus needs to be correctly terminated. 120 Ohm resistor needs to be present on each end of the line. To verify correct termination you can switch off the power of all connected modules and measure resistance across L and H terminals. The result should be 60 Ohm. Please note this only tells you if correct amount of resistors is used, it will not give you information about their location.
• Ensure the L and H terminals are not swapped anywhere along the length of the bus.

If you still cannot identify the problems you can use a CAN to USB converter to analyse the traffic on the CAN bus to find the root cause of the issue.