ComAp InteliGen 500 G2

Paralleling generator set controller

InteliGen 500 G2 is a paralleling controller for single or multiple diesel generator sets in grid-tied or island operation. ComAp documents Modbus RTU/TCP communications, several hardware communication ports and a configuration archive workflow. Monitoring must be bound to the installed application, firmware and exported object definitions.

  • Modbus TCP
  • Modbus RTU

Paralleling generator set controller

Compatibility

Documented Modbus RTU and TCP communications

The exact product page and datasheet list Modbus RTU/TCP among the controller communication protocols. Edge requires an approved read-only point list for the installed application and firmware; no generic register map or preconfigured import is asserted.

InteliGen 500 G2 order code IG4500XXBAA under the cited July 2026 datasheet. The controller can run different applications and optional feature bundles. Confirm hardware modules, application, firmware and InteliConfig archive before defining points. Do not write start, stop, breaker, synchronising, load-share, forced-value, PLC or setpoint objects from this monitoring path.

Connect it with

Route into Edge

When the commissioned Ethernet interface exposes the approved read-only objects

  • Modbus
  • Edge
  • Platforms
Paralleling generator set controller
Interface
Gateway
Edge
Output
InteliGen 500 G2InteliGen 500 G2
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Gateway
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Use the configured controller endpoint and a point allowlist exported for the installed application. Keep operational control and configuration tools on their engineered path. The customer-platform output is optional; Edge remains the local system of record.

When a serial port is assigned to an approved monitoring client

  • Modbus
  • Edge
  • Platforms
Paralleling generator set controller
Interface
Gateway
Edge
Output
InteliGen 500 G2InteliGen 500 G2
Isolated serial interfaceApproved RS-485-to-host adapter
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Gateway
Customer platformMQTT · API · files
Modbus RTU · RS-485
Isolated serial
Runs locally
Optional onward data
Match the commissioned serial settings and use an isolated interface. Do not infer an RTU map from the controller's separate Modbus Client feature for third-party devices. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
InteliGen 500 G2, IG4500XXBAAModbus RTU/TCP, Ethernet, USB, RS-232/485, CAN and optional communications modulesBind monitoring to the installed application, firmware and exported object list.
InteliGen 500, InteliGen NT GC and InteliGen NTC GCEarlier controller generationsDo not reuse G2 firmware or communications assumptions for predecessor hardware.
InteliGen 500 G2 with Suite or communications modulesOptional redundancy, signal sharing and remote communications functionsRecord licensed features and module types before commissioning.

Specifications

ComAp documents both a Modbus server protocol and a separate Modbus Client feature for controlling third-party devices. Only the controller's approved monitoring surface belongs in this guide.12

Exact product
InteliGen 500 G2, order code IG4500XXBAA12
Applications
Single or multiple diesel gensets in grid-tied or island operation12
Monitoring protocols
Modbus RTU/TCP; SNMP v1, v2c and v3 are also listed2
Scale
Cooperation with up to 32 genset, mains or tie controllers is published for supported applications1
Configuration continuity
Firmware workflow uses a configuration backup and archive restore, with manual intervention sometimes required1
Environment
-20 to +70 °C operating range; IP65 front protection when properly installed2

Interface

Documented measurements and integration boundaries for InteliGen 500 G2.

  • Generator and mains voltage, current, frequency, active power, reactive power, apparent power and power factor where exposed by the installed application.
  • Engine speed, run hours, battery voltage, temperatures, pressures and supported ECU values where configured.
  • Controller mode, generator availability, breaker feedback, alarm and shutdown states as read-only observations.
  • Fleet identity should include controller order code, firmware, application and configuration archive revision.
  • Start, stop, breaker, synchronising, load-share, forced-value and setpoint objects remain outside this guide.

Assessment

InteliGen 500 G2 IG4500XXBAA with site-approved Modbus objects; no generator, breaker, synchronising, load-share or setpoint control.

InteroperabilitySupported with conditions
The exact product supports Modbus RTU/TCP, but the retained public sources do not provide a fixed universal server map for every application.12
AccuracySupported with conditions
Generator, mains and engine measurements are part of the controller role; usable external objects depend on application and metering setup.2
SecuritySupported with conditions
ComAp publishes role-based users, password policy, audit and signed firmware features, while Modbus monitoring still needs network isolation and read-only enforcement.12
ReliabilitySupported with conditions
Redundancy options, configuration backup, diagnostics and environmental limits are documented; recovery depends on the installed application and archive.12
RuggednessSupported with conditions
The datasheet publishes panel protection, temperature, humidity, vibration and shock limits subject to correct installation.2
ScalabilitySupported with conditions
Cooperation with up to 32 controllers and multiple communication options is documented; polling and address plans remain site-specific.12
LifecycleSupported with conditions
ComAp publishes current firmware, configuration tools, upgrade and rollback guidance; retained archives are needed for replacement continuity.1

Setup

  1. Confirm order code IG4500XXBAA and record the installed hardware modules, application, firmware and InteliConfig configuration archive.

    Do not treat predecessor InteliGen products as the same controller.

  2. Have the generator controls owner identify the Modbus server interface and provide the approved read-only object or register list for this application.

    The controller's Modbus Client function is a separate role.

  3. For TCP, use a protected controls network.

    For RTU, record address, baud rate, parity, termination, bias and isolation. Keep monitoring traffic within the controller engineer's polling budget.

  4. Read identity, mode and a small set of measurements first.

    Compare electrical values, engine state and breaker feedback with the controller display in a safe operating state.

  5. Disable all writes in the Edge client.

    Revalidate the point list after firmware, application, feature licence, module or configuration archive changes.

Common questions

Does the Modbus Client feature define the Edge connection?
No. ComAp describes that feature as the controller controlling third-party devices. Edge monitoring uses the controller's approved server surface and must not inherit client-role assumptions.12
Can one register list be reused across every InteliGen 500 G2?
Not from the evidence retained here. Applications, firmware and optional modules can change the available objects, so the commissioned export is part of the integration record.12
Does protocol access authorise generator control?
No. This guide publishes monitoring only. Start, stop, breaker and synchronising functions require a separate control design and physical acceptance process.2

Sources

  1. InteliGen 500 G2 product and resource page (opens in a new tab) ComAp
  2. InteliGen 500 G2 datasheet (opens in a new tab) ComAp

Further reading

Product names and trademarks belong to their owners. Publication does not imply endorsement or a commercial relationship.