Cummins PowerCommand 3.3

Compatibility

Direct Edge integration not yet verified

Cummins A029X159 issue 26, chapter 13, documents PC 3.x/PCC3300 measurements, scaling and unavailable-value codes. It explicitly includes PCC3300V1 and V2 unless a row is marked V2 only. Direct Edge commissioning remains a site task; the published map provides the point definitions.

Use A029X159 issue 26 (June 2020), chapter 13, as a best-effort starting map and compare initial reads with the installed HMI. Record the controller identity and existing serial settings. Keep one monitoring client on the protected RTU segment and exclude generator, breaker, reset, synchronising, load-share and parameter writes.

Models

Specifications

Cummins describes PowerCommand 3.3 as an integrated generator set monitoring, metering and control system that also performs protection, governing, synchronising, load sharing and power transfer functions.^1, 3

Exact family

PowerCommand 3.3, also identified by Cummins as PCC 3300 or PC 3.3; hardware and software revision must be recorded²

Published external interface

Modbus interface; Cummins Cloud documentation connects PCC 3300 and PC 3.3 over Modbus RTU^2, 3

Control scope

Integrated voltage regulation, governing, protection, synchronising, load sharing, breaker and power-transfer functions depending on application^1, 3

MLD scope

Additional s-CAN information sharing and automatic load-demand operation for up to 16 paralleled generator sets¹

Evidence gap

No retained public revision-matched register map, function permissions, scaling, unavailable-value behavior or security contract²

Interface

Documented measurements and integration boundaries for PowerCommand 3.3.

• Documented PC 3.x entries include L1-N voltage 40018 (unsigned, 1 V), total power 40034 (signed, 1 kW), and frequency 40044 (unsigned, Modbus-specific 0.1 Hz).
• Engine running time spans 40070/40071, unsigned 32-bit, high word first, scaled by 0.1 seconds. The map also defines engine observations and fault/status entries; select the rows marked PC 3.x.
• Controller mode, synchronising state, generator and utility breaker feedback, alarms and transfer status must remain observations only and must be traced to the commissioned application logic.
• Remote start, stop, reset, breaker operation, synchronising, load sharing, voltage and frequency regulation, power setpoints, transfer and all parameter or output writes remain outside this guide.

Setup

1. Record the exact control identity

   Photograph the generator set and controller nameplates. Record the generator model and serial number, PCC 3300 hardware and software revision, HMI revision, application mode and installed communications option.

2. Use the published PC 3.x map

   A029X159 issue 26 is publicly available. Chapter 13 specifies PC 3.x and covers PCC3300V1/V2; use only the applicable rows. Its holding-register references follow the 4xxxx convention: reference 40018 corresponds to zero-based wire offset 17. A client using one-based offsets uses 18. Start with a small FC03 read and compare with the HMI.

3. Separate monitoring from operation

   Have the generator controls owner define a read-only point allowlist and protected communications segment. Exclude all start, stop, reset, breaker, synchronising, load-share, transfer, setpoint, parameter and output writes.

4. Read voltage and power

   Start with voltage and power. For L1-N voltage use FC03, wire offset 17, quantity 1, PDU 03 00 11 00 01; synthetic 00 E6 gives 230 V. Total power uses wire offset 33, quantity 1: synthetic FF F6 decodes as signed -10 kW. Frequency reference 40044 uses wire offset 43: raw 500 gives 50 Hz using the row’s explicit Modbus multiplier 0.1, not the 0.01 shown for the other data link. Compare stable readings with the HMI.

Common questions

Can Edge read a PowerCommand 3.3 over Modbus RTU?

The public Cummins map provides a practical RTU starting point for PC 3.x/PCC3300. Use its holding-register rows, address convention and quality codes, then compare voltage and power with the local HMI. This guide does not supply an imported Edge profile or claim a field-tested installation.^2, 3, 4

Does this guide allow remote generator or breaker control?

No. PowerCommand 3.3 integrates generator, breaker, synchronising, load-share and transfer functions, but this guide authorises no operational write. Any control project requires a separate engineered, interlocked and physically witnessed acceptance process.^1, 3

Is the Masterless Load Demand s-CAN network an Edge interface?

No. Cummins describes s-CAN as a controls network that shares information among MLD-capable generator sets. It is not established here as a third-party monitoring route.¹