Change log
Every change to the PPC: who (user, API key, grid operator over Modbus, or the PPC itself), from where, what changed (old -> new) and the result. Refused attempts are listed too.
| Time | User | Level | Source | Action | What changed | Result |
|---|
Users
Viewer: sees everything. Operator: also runs the plant (setpoints, dispatch, enables, Local / Remote, start / stop). Engineer: also changes the configuration. Admin: also manages users. A changed user is signed out at once.
| User | Name | Level | Account | Last sign-in |
|---|
Add a user
PPC licence
Install a new licence file (MaxPpc.dll). It is checked first; the old file is kept beside it as .bak. Restart the PPC (the Windows service, or the Tray) to use it.
Controls and setpoints in force
What the PPC works to now - set on the Setpoints page or by the grid operator (Remote)Live trend — last 10 minutes
Built in this browser from the 2 s pollInverters
Bar: actual as % of max MW, marker: setpoint. Red = left out of the split, with the reason.Plant
Control mode
Setpoints are accepted only in Remote mode. Dispatch (Dispatch page) works in Local and Remote.
Control enables
A disabled control refuses its setpoint (this page and the grid operator's Modbus writes). Stored with the config.
Setpoints
The site's own setpoints: accepted in Local mode (the site has control) with that control enabled. In Remote the grid operator's setpoints are used and these are refused.
Plant dispatch
Devices
| Device | P setpoint (MW) | P actual (MW) | Q setpoint (MVAr) | Q actual (MVAr) | Comms | In the split |
|---|
One device by hand
Writes P and / or Q to one device (manual override). Leave a box empty to leave that value alone.
Recording
Active power
Reactive power
Voltage and power factor
Frequency response (grid tests)
Ramp rate settings
Plant
Devices
The inverters (and meters) the PPC controls. Type and Availability are read only: the type comes from Plant setup (Setup page), availability from the PPC. Registers, status codes and enable writes of a device stay as they are when you edit it here. Q cap is used only with "Reactive power cap" on (Control and deadbands).
| Name | Group | Connection | Unit id | Max MW | Enabled | P control | Q control | Q cap MVAr (0 = Max) | Type | Availability |
|---|
Connections
IP address, port and timeout of each connection the PPC reads and writes through (inverters / station masters, POI meter). A change is saved at once but takes effect after a restart of the PPC (its connections are open): "Running now" shows what it uses until then. Two connections may not use the same IP:port. The devices on each connection are listed so you change the right one.
| Connection | Type | IP address | Port | Timeout ms | Running now | Status | Devices |
|---|
Point of connection meter (power analyzer)
The tags the PPC reads as feedback at the POI. P / Q / V / PF drive the Status page and the closed loop; grid frequency drives frequency response; scale converts the tag value to MW / MVAr / kV. Live = tag value x scale. A Bad or stale tag reads as 0 in the PPC. Empty tag = not used.
| Quantity | Tag | Scale | Live | Quality |
|---|
Control and deadbands
Frequency test (grid compliance)
For the frequency response test: the PPC acts as if the grid were at measured frequency + offset. The grid operator still reads the real frequency. Switches off by itself after the duration; not saved.
Command registers and handling
Holding registers (0-based) on the PPC's Modbus slave where the grid operator / SCADA writes its setpoints, the coils of the single-style commands, and how grid commands are handled. Throttle = minimum time between accepted grid setpoints. Timeout = no grid command for this long counts as comms loss (0 = off).
Grid operator interface
Loading…Q, voltage and PF control are exclusive: enabling one disables the other two; status register bits 3-7 report P / Q / V / PF / ramp enabled.
| Function | Area | Address ✎ | Type | Scale ✎ | Access | Name | Unit | Note |
|---|
Type a new address in the blue column, then Save. Commands move their own setting; feedback and status entries are stored as overrides; one pulse / feedback coil moves its whole double block. Overlaps are refused and nothing changes.
Value entries can be sent as Float32 or as an integer: register = value x scale (e.g. Int16 x100: 1.25 MW -> 125).
Slave map (extra tags on the Modbus slave)
Tags this PPC publishes on its Modbus slave besides the grid map: address (0-based holding register), data type, byte order, read-only and scale (register = value x scale). Saved as one list: on an address conflict nothing changes.
| Tag | Address | Data type | Byte order | Read-only | Scale |
|---|
Export / import the PPC setup
Export downloads ONE file with plant settings and control, inverters with their registers, POI meter, grid map, connections, extra tags, the Modbus slave map and this site's device types - not users, passwords, history or the licence. Import shows what changes per section first; Apply needs the plant stopped and saves the current setup to ppc-config-backups\ first (import that file to undo). A ppc_config_v3.json (PPC config alone) can be imported too.
Import
Sections to import
Plant setup by type
Pick the inverter or POI meter type, where it is wired and its unit ids. Preview shows what would change (nothing is changed); Apply makes it live and writes it to the change log.
Import register list
Read the vendor's or grid operator's register list (Excel, CSV or PDF). The PPC suggests which register is which; you confirm every row. Nothing changes until you save.