Solar Trackers and Park Controllers

On a PV plant built on single-axis trackers, Mirox follows every tracker row as a component of its own — where it points, where it should point and whether its drive is healthy. Where the plant has one, the park controller that drives the whole field is monitored beside the rows. Both are optional: a plant without trackers shows none of this, and a plant without a park controller is complete without one.

Solar Trackers

A solar tracker is one single-axis tracker row. Like an inverter it is a flat component of the solar plant, discovered automatically from the data source that reports it — you do not enter the rows by hand. A tracker is identified by the serial number of its row controller, not by its place in the field: the site, row and position are shown as information, so a re-numbered field keeps every tracker's history.

Mirox records nine series per tracker:

Series	What it tells you
Angle	Where the row points now (°)
Angle setpoint	Where the field controller wants it to point (°)
Motor current	The drive's current (A)
Battery state of charge	The backup battery of the row controller (%)
Battery voltage	The same battery's voltage (V)
Controller temperature	The row controller's temperature (°C)
Vendor status	The maker's own error word, as the controller reports it
Operating state	The platform's standard state, the same scale as inverters, wind turbines and battery converters
Condition flags	The tracker's conditions packed into one word: emergency stop, offline, battery absent, battery low, weak radio link, misaligned

What the operating state means

The tracker is …	Operating state
tracking the sun	Producing
stowed by the field controller — for wind, snow or low light	Producing, limited by someone else (shown as Capped externally)
held by an override, a cleaning run or an emergency stop	Stopped by command
reporting an error word	Fault
not delivering a record	no state — a gap, never a value

A stow is the field protecting itself and is never a fault. How the series are named and decoded for your own dashboards is listed under Metric Collection — Solar Tracker Metrics.

Park Controllers

A park controller is the central controller of one technology of the plant. It comes in four kinds — Tracker field, Battery plant, PV plant and Wind plant — and exists only on centralised systems: a field whose rows obey one central controller, a storage plant run by one plant controller. A decentralised plant has none, and nothing in Mirox requires one.

A park controller is identified by the plant and its kind (and, on a plant split into segments, the segment it controls). Mirox records exactly four series per controller:

the vendor status — the maker's own word, unchanged;
the operating state — the platform's standard state;
the condition flags — the controller's conditions in one word with the same meaning on every plant: running, standby, night mode, starting, stopping, stopped, alarm, fault, stow for wind, snow or low irradiation, override, cleaning, state of charge high or low, switchgear open, communication degraded, manual mode;
the measurements the controller itself provides, each named by a quantity: state of charge, state of energy and state of health; available charge and discharge power; units connected and running, storage units connected; auxiliary energy today; converter and storage availability; and, for a tracker field, the wind speed, irradiation, temperature and precipitation the controller decides on, the remaining stow lock time and the communication error rate of its row controllers.

What the Pages Show

The Trackers page

A solar plant with trackers gets a Trackers entry in its left-hand navigation. The page holds:

the park controller card, when the plant has a tracker-field controller (see below);
one graph with a metric toggle — Angle, Setpoint, Motor current, Battery SoC, Battery voltage, Temperature — drawing one line per tracker over the time range you pick;
the tracker table: the tracker's name with its identifier, Site · Row · Position (with its control group beneath), the hardware with its firmware, Angle / setpoint, the battery's state of charge, Status — the maker's word and code, the standard state and the set condition flags as badges — and Last seen. With the permission to create tickets, the row menu opens Create Ticket for that tracker; a tracker with an open ticket carries a ticket badge.

Hidden trackers are left out of this page.

Components page

On a plant with trackers, the Components section has a Trackers tab with the same table, searchable, sortable, paged, and with the Show Hidden switch.

The park controller card

The card appears only where the plant has a park controller of the page's kind — on the Trackers page for a Tracker field, on the Battery page for a Battery plant. It shows the controller's name, its kind and maker, its operating state, the set condition flags, the maker's own status text and code, the measurements it provides, and when it last reported. A plant without a controller shows no card and no placeholder.

Alarms and Notifications

Trackers and park controllers are judged like every other unit — from the state the data say, not from each raw code.

Trackers. One row of hundreds is a service item, so a tracker's events stay at Normal or below and never notify on their own. Trackers are also never members of the plant's "components down" summary: a parked row costs a little yield, not the plant.

Tracker stopped by fault (Normal) — the error word stays set for two field refreshes, about 10 minutes.
Tracker not communicating (Normal) — no record for three refreshes, about 15 minutes, while the rest of the field keeps refreshing.
Tracker misaligned (Low) — at least 10° off its setpoint for three refreshes, about 15 minutes, while it is tracking and no stow, override or cleaning stands on the field controller.
Tracker safety alarm (Critical, notifies) — a danger class reported by the row. No tracker reports one today; the alarm exists so a future controller that does is handled like every other unit.

Park controllers. One controller stands for the whole field or the whole storage, so its fault is a plant situation:

Park controller fault (Critical, notifies on its own) — the controller reports the plant in fault for two consecutive one-minute reads. There is no summary to fold it into, so the notice is sent alone, with a resolution notice when it clears.
Park controller not communicating (Normal) — no reading for 15 minutes.
Park controller safety alarm (Critical, notifies) — a danger the controller reports on the plant level: a fire alarm, smoke or gas detection, a released fire suppression.
Park controller stopped by command (Low, never notifies) — standby, night mode, a stow for wind, snow or low light, an operator override or a cleaning run. It is the explanation the other checks read: a tracker that stands still while the field is stowed is not misaligned.

The maker's own alarm and warning list of both is filed under the Vendor alarms category and does not notify. When the platform's view of a plant's trackers or park controllers changes, or someone edits one, the change is recorded under the Components category. Events on a tracker or a park controller open their page — the Trackers page, or the Battery page for a battery-plant controller — and both can be linked to tickets like every other component. Levels and timing: Alarm Levels — Solar trackers and park controllers.

Data Collection

Trackers and park controllers reach Mirox through the adapter of the system that controls them. The first fielded systems are a Zimmermann tracker field read through a Gantner Q.reader and a Nidec battery plant controller; other makers follow the same model. See the Data Scraper for how the edge agent collects and standardizes plant data.

Solar Plants — the plant type trackers belong to
Battery Storage — where a battery-plant controller is shown
Alarm Levels — levels, timing and which events notify
Events — every event family the platform records
Metric Collection — the series names and labels