ComAp InteliGen 500 G2

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

• 
  Modbus Interface ZMB-3X
  From €399 ex VAT Configure Modbus Interface
• 
  Gateway ZGW-20
  From €899 ex VAT Configure Gateway
• Evaluation Gateway on a Raspberry Pi Edge with one device licensed
  Free Set up Evaluation Gateway on a Raspberry Pi

Models

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.^1, 2

Exact product

InteliGen 500 G2, order code IG4500XXBAA^1, 2

Applications

Single or multiple diesel gensets in grid-tied or island operation^1, 2

Monitoring protocols

Modbus RTU/TCP; SNMP v1, v2c and v3 are also listed²

Scale

Cooperation with up to 32 genset, mains or tie controllers is published for supported applications¹

Configuration continuity

Firmware workflow uses a configuration backup and archive restore, with manual intervention sometimes required¹

Environment

-20 to +70 °C operating range; IP65 front protection when properly installed²

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.

Setup

1. Record controller identity.

   Confirm order code IG4500XXBAA and retain the application, firmware, module types and InteliConfig archive with the monitoring record.

2. Obtain the monitoring object list.

   Use the existing application’s Modbus server objects for a first read. The optional Modbus Client feature connects the controller to other devices; it is a separate role and does not define these server addresses.

3. Check the communications module.

   ComAp’s connection FAQ identifies controller setpoints or InteliConfig for CM-Ethernet settings and TCP port 502 for Modbus. Check the installed module’s settings before testing the private endpoint; do not expose it to the internet. For RTU, record address, baud rate, parity, termination and isolation.

4. Compare generator and mains readings.

   Read mode, generator voltage, frequency and active power first using the available object list. Compare each with the matching controller display, then compare generator power with the generator feeder meter during an existing run. Keep mains import separate: it can include other generators, loads and PV. Preserve units, signs and timestamps in the monitoring record.

5. Keep the configuration record.

   Use read-only requests and retain the object list with the configuration archive. Check the same small measurement set after an application or firmware change. ComAp’s current Global Guide download requires a free account; obtain it for register addresses, data types and the export procedure rather than borrowing a predecessor map.

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.^1, 2

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.^1, 2

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.²