Quick answer
A device that collects, stores, and transmits performance data from a solar PV system — recording production, voltage, current, temperature, and environmental conditions at regular intervals for monitoring, troubleshooting, and performance verification.
Answer: A solar data logger records timestamped measurements from connected equipment and makes them available for monitoring and analysis. What it records depends on the inverters, meters, sensors and interfaces installed. A logger may transfer data to a portal, but it does not automatically measure every parameter or make the measurements suitable for billing.
Logger, meter and monitoring platform
A meter or sensor supplies a measurement. A logger collects and records it. A monitoring platform presents the records, trends and alerts. Some products combine these roles, so check the actual model rather than assuming a separate box is always needed.
SMA’s Data Manager M documentation describes a logger that also serves as a system manager and gateway, with supported inverters, meters and sensors. Fronius’s Datamanager documentation describes transfer to Solar.web using an internet connection and interfaces for third-party systems. These are vendor-specific examples, not evidence that all loggers support every inverter.
What should you check before choosing one?
| Question | Why it matters |
|---|---|
| Which devices and firmware are supported? | A communication connector alone does not establish compatibility |
| Which measurements are available? | String-level or environmental data needs suitable source equipment |
| What are the sampling and recording intervals? | Recorded averages may conceal short events |
| What happens during an internet outage? | Local storage and later upload behaviour need confirmation |
| Can records be exported? | Ownership, retention and access affect later analysis |
| Who receives alerts? | A dashboard needs a defined operational response |
| What recurring costs apply? | Cloud subscriptions and cellular plans belong in the operating budget |
A standalone logger does not inherently improve sensor or meter accuracy. For billing or a performance contract, obtain the required measurement accuracy, metering arrangement and audit trail from the relevant contract or programme. Fast recording alone does not make a system revenue-grade.
A storage calculation
For a hypothetical logger storing 20 numerical parameters every five minutes, there are 288 records per parameter per day. At eight bytes per parameter value, five years using 365 days per year requires:
20 × 288 × 365 × 5 × 8 = 84,096,000 bytes, or about 84.1 MB in decimal units.
This is the numerical payload only. Timestamps, quality flags, database overhead, backups and additional records increase the actual requirement. Confirm retention against the device’s specified behaviour.
Commissioning and troubleshooting
Verify device identities, channel names, units, timestamps and measurement direction before handover. Compare a recorded value with the source device and check whether the portal shows current or delayed data. Test the agreed alert recipients and document who owns the accounts.
A missing portal reading does not by itself prove the PV system stopped generating. Check equipment status, local records and the communication path separately. Likewise, an unexplained low reading needs investigation; the logger alone does not establish whether shading, weather, equipment failure or configuration caused it.
Related concepts include smart meters and solar irradiance. When evaluating a solar design workflow, define the monitoring and handover information your team needs and verify the software’s supported outputs. Do not assume design software supplies live operational monitoring.
Reviewed 30 September 2026. Product examples are based on the linked manufacturer documentation. Compatibility, retention, billing requirements and installed measurement capability must be checked for the specific system.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
