
Solar Pump Fault Log Time Alignment: Separate Event Time from Upload Time
Solar pump fault log time alignment helps service teams determine whether a controller alarm, a falling water level, a change in flow, and a remote notification occurred in the order a dashboard suggests. Devices may use different clocks, time zones, recording intervals, or upload delays. Sorting exported rows by the time they reached a server can therefore create a misleading failure sequence even when every individual record is genuine.

This guide addresses evidence handling for intermittent solar pumping faults. It does not diagnose an electrical fault from timestamps alone or assume that every RUTANPUMP controller has a clock, network connection, or downloadable event history. The product photograph illustrates a pump family, not logging hardware or a completed diagnostic test. Use only the supported data interfaces and approved service procedures for the installed equipment.
Four timestamps that should not be merged
Event time is when the source device says something happened. Sample time is when a measurement was taken. Reception time is when a gateway or server received a message. Export time is when a file was generated. These can be identical in a simple local record, but remote sites with intermittent communications often separate them by seconds, minutes, or longer.
A delayed alarm notification is not automatically a delayed protective action. Conversely, a fast notification does not prove when the local controller detected the condition or stopped the motor. Keep those questions separate in a service case. Request the meaning of each timestamp field from the equipment documentation rather than assuming that a column called time is the event clock.
The NIST guide to computer security log management explains the dependence of recorded timestamps on host clocks. Its logging principles are useful for preserving a multi-device record. It is not a solar pump performance standard, a required pump communication protocol, or evidence of a particular controller feature.
Preserve the raw files before correcting a clock
Keep original exports in their original format, with the equipment identity, file date, and method of collection. Work on a separate analysis copy. Record any known time-zone setting, manual clock adjustment, firmware change, power interruption, or gateway replacement. If a service tool converts local time to another format, preserve the settings used in that conversion.
Do not overwrite the original event time with a guessed corrected value. Add separate columns for normalized time, correction method, and uncertainty. A later reviewer must be able to distinguish what the device recorded from what the analyst inferred. Where only a photograph of a display exists, identify the photograph's time source and limitations instead of presenting it as a synchronized electronic trace.
Do not clear a history, reset protection, change operating settings, or cycle power just to create a cleaner graph. The authorized service procedure may require some of those actions, but first preserve available evidence and record the action. A reset can create a new clock segment or discard volatile records, making the original sequence harder to reconstruct.
Clock and record inventory worksheet
Before comparing events, complete one entry for each controller, logger, gateway, water-level instrument, flow recorder, or manually recorded observation. Leave unsupported features marked unavailable rather than inventing data.
Record source: Pump controller; Fields to capture: Device identity, firmware and event-field definition; Question to resolve: Is the time a clock, uptime or sequence number?
Record source: Hydraulic logger; Fields to capture: Sample interval, timestamp reference and units; Question to resolve: When was each level or flow value actually sampled?
Record source: Gateway; Fields to capture: Reception time, buffering and reconnect record; Question to resolve: Were old messages uploaded after a communication gap?
Record source: Server export; Fields to capture: Time zone, conversion and export settings; Question to resolve: Has local time already been converted?
Record source: Manual observation; Fields to capture: Observer record, clock source and approximate timing; Question to resolve: What timing precision can the observation support?
Record source: Power transition; Fields to capture: Restart indication and counter behavior; Question to resolve: Did a clock reset, jump or stop while offline?
Record source: Analysis copy; Fields to capture: Correction, evidence and uncertainty; Question to resolve: Can another reviewer reproduce the alignment?
For sites without electronic logs, the same worksheet can describe a planned observation period using approved instruments and existing displays. Record the limits of the resulting evidence. Do not claim sub-second sequencing from hand-written minute-resolution notes.
Establish a common reference without changing controls
Use a documented time reference for the analysis, commonly UTC with an explicit offset for local display. Preserve the source time-zone value, including any daylight-saving treatment where relevant. A timestamp without its offset can be ambiguous when files come from equipment configured in different countries or serviced by different organizations.
The NIST operational technology security guide discusses the importance of accurate system clocks for event and log timestamps. Its operational-technology context also reinforces that changing a networked control environment is not an ordinary spreadsheet operation. Any alteration to device time synchronization must follow the site's authorized control and cybersecurity process.
Where a supported clock comparison is available, record the source clock and reference clock at the same observation point. Establish the sign of the correction explicitly. If the source clock reads two minutes ahead of the reference, subtract two minutes when creating the analysis column. Keep the measured offset separate from an assumption that the clock remained equally wrong throughout an earlier incident.
A hypothetical delayed-upload sequence
Assume a controller records an alarm at 10:02:20 on its local clock, and a documented comparison shows that clock is two minutes ahead of the analysis reference. The corrected event time would be 10:00:20, subject to the evidence supporting that offset. Suppose the gateway receives the buffered message at 10:05:00 after reconnecting. These numbers are hypothetical and do not describe a RUTANPUMP installation.
A water-level logger records a sample at 10:00:00 and another at 10:01:00 on a confirmed reference clock. Those samples describe a one-minute observation interval. They do not reveal the exact instant a level crossed a threshold between them. The corrected controller time falls inside the interval, while the gateway reception occurs later. Sorting only by reception could incorrectly suggest that the hydraulic change preceded a much later controller response.
This example establishes why the timeline needs correction and uncertainty, not the cause of the alarm. Sensor lag, sampling intervals, controller detection logic, and communication behavior still matter. An aligned sequence can support a hypothesis; it cannot prove that one recorded condition caused another without the relevant electrical, hydraulic, and control evidence.
Handle resets and drift as separate segments
One constant correction is unsuitable when a source clock restarts from a default value, jumps after synchronization, or drifts measurably during the observation period. Divide the record into segments supported by known clock behavior. Retain the restart boundary, sequence counter, and any independent observations that connect the segments. Mark a segment unaligned if its reference cannot be recovered reliably.
Do not force continuity by dragging a trace until its peaks line up with another signal. A visually persuasive alignment can hide the very delay being investigated. Correlation between flow and controller current, for example, may reflect hydraulic response or changing sunlight rather than a clock error. Select the alignment method from independent timing evidence before interpreting the physical relationship.
Choose the next diagnostic step from evidence
Once time fields are understood, compare the corrected incident window with controller status, available PV measurements, supported operating data, source-water observations, valve state, and flow. Apply the controller error-code diagnostic workflow for the broader fault-isolation context. Exact code definitions remain model-specific.
For a service return, link the timeline to the warranty evidence and triage guide. Include raw records, the analysis copy, clock-reference evidence, unavailable channels, and tests already authorized. Remove passwords and unnecessary personal information before sharing files. Do not expose a controller to the internet or add remote access merely to obtain a log.
Frequently asked questions
Is the time a dashboard receives an alarm the time the pump tripped?
Not necessarily. Reception can follow local detection and protective action, particularly when messages are buffered. Confirm the field definition and preserve source event time separately.
Can all records be corrected using one measured clock offset?
Only where evidence supports that clock behavior over the relevant interval. Resets, synchronization jumps and drift may require separate segments or an explicit unresolved timing range.
Does an aligned timeline prove the root cause?
No. It helps establish possible order and timing limitations. Electrical, hydraulic, sensor and controller evidence are still required to evaluate the cause of a fault.
Send a time-aware service record
Contact RUTANPUMP / Wenling Jingzhan Mechanical & Electrical Co., Ltd. through the solar pump service inquiry page. Include equipment identity, supported log fields, clock worksheet, raw exports and the specific service question. Email: sales@rutanpump.com. WhatsApp/WeChat: +86 18267835331. Telephone: +86 (0576) 86322398.
留言