Frequently Asked Questions

Each ComAp device usually allows for multiple ways of connection. The simplest one supported by the majority of our devices is the RS232 (serial) connection. For this, you need an RS232 cable (null modem) and if your PC is not equipped with an RS232 port you need a USB<->RS232 converter.
USB connections are very common. 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 require you to use a communication module (plug-in eg a RS232 card) or communication bridge (external device eg Internet Bridge NT). Not all types of connection are possible on each device. You can find all the details related to this topic in your device's Comprehensive guide or Communication guide.
 
Detailed information about connection to:
InteliLite NT, InteliATS NT, InteliCompact NT is available IL-NT, IA-NT, IC-NT Communication Guide (page 21)
InteliGen-NT, InteliSys-NT, InteliMains-NT is available in IGS-NT Communication Guide (page 19)
InteliLite is available in Global Guide InteliLite AMF25 Global Guide (page 126)

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

It usually consists of several steps:

• Create a controller back up.
• Update the device firmware. It will contain default Configuration Archive and default Application.
• Change the Application (SPtM, MiNT, MCB, MGCB, BTB, etc) to the 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 its original state before the firmware upgrade was attempted.

You will need the following information about your device:

• serial number
• "password decode" number

Both numbers can be obtained through the monitoring software relevant to the device.

• Serial number is available in Controller info
• Password decode number is available in Values / Info

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.

Typically, you connect the ECU directly to the controller using CAN bus. If the ECU does not support the J1939 communication protocol you need to use a communication interface either on the ECU side (such as SAM CCB2 or SmartConnect modules) or on the ComAp side using the I-CB communication bridge.

The communication is typically bi-directional so we support reading of values from the ECU as well as sending commands to the ECU (Start, Stop, etc) 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.

 

• Make sure you have the latest firmware in the controller itself but also in all the communication modules (plug-in, built-in or external).
  • Communication modules that supports connection via the internet
    • CM-4G-GPS
    • CM-Ethernet
    • CM-GPRS
    • InternetBridge-NT 4G
    • InternetBridge-NT
    • IB-Lite
    • IB-COM (Built-in communication module for NTC controllers)
    • IL-NT GPRS
• Ensure the communication interface is configured correctly.
  • CM-4G-GPS, CM-Ethernet, CM-GPRS - Can be set in the controllers setpoints on the unit itself or using InteliConfig configuration software.
  • IB-COM, IB-Lite - Use web interface -  just connect to http://<controller-ip-address>/sp_index.htm using your favourite web browser.
  • InternetBridge-NT 4G, InternetBridge-NT - Requires a software tool called IBNTConfig(https://www.comap-control.com/products/detail/ib-nt-config) 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 a gen-set to mains (or multiple gensets to each other) 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 a 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.

• InteliCompact-NT
• IG200
• InteliGen-NT + InteliSys-NT
• IS2GAS

The same document also contains the list of supported AVRs and Speed Governors including the wiring and configuration setpoints.

ComAp controls incorporate the AirGate connection technology to make access to the internet as simple as possible. AirGate was designed to overcome the issues commonly faced when trying to connect remote equipment using internet based communications.

AirGate allows our controllers to connect to the internet using the existing network infrastructure, negotiating firewalls and VPN systems and removing the requirement for static and public IP addresses.

Once AirGate in the controller is activated even if the IP address is changed, our configuration and monitoring tools will keep track of the remote equipment.

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.

 

The description above is not enough? Try our Booot jumper training video.

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)…

InteliConfig: When you are connected to the controller or have its archive open in InteliConfig please click on: Tools -> Generate Cfg image (MODBUS)

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.

Please ensure the following requirements are met:

• Use of the correct cable – we recommend a shielded CAN bus cable.
  • Recommended data cables: BELDEN - for shorter distances: 3105A Paired - EIA Industrial RS-485 PLTC/CM (1x2 conductors); for longer distances: 3106A Paired - EIA Industrial RS-485 PLTC/CM (1x2+1 conductors)
  • The bus topology needs to be strictly linear, no branching, no ‘star’ topology.
  • The CAN bus needs to be correctly terminated. A 120 Ohm resistor needs to be present on each end of the line. To verify correct termination, you can switch off the power to all connected modules and measure the resistance across the L and H terminals. The result should be 60 Ohm. Please note this only tells you if the 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 problem, you can use a CAN to USB converter to analyse the traffic on the CAN bus to find the root cause of the issue.