System clock time lost

The inverter has lost its date and time. On Fronius units this shows up as status code 751, a warning on the display. A wrong system time directly corrupts data logging and the reported power generation values, so a monitoring record with odd time stamps can be the first sign of it. The usual cause is the clock's backup store running flat during a long power outage. Eaton names a drained supercap for this, and FIMER names the clock battery. Separate a simple time loss from a real-time clock failure by the code. A 751 warning only needs the time reset. A 758 means the clock module is in emergency mode and feed-in continues normally. A 757 is a clock hardware error, and the inverter stops feeding the grid. Check first by resetting the date and time on the inverter. If the code keeps coming back, contact a trained service technician. On a FIMER inverter, switch it fully off on both AC and DC, wait, and restart it. If the clock has gone back to 01/01/2000, replace the battery with the unit fully off and the polarity correct. Where the device supports it, use SNTP time sync to keep the clock right. Only move the time back when you have to, because that can overwrite system data already recorded.

<!-- review notes

• sentence 2: support check: partial - u19 says wrong system time directly affects data logging and power generation value, but the claim that a monitoring record with odd time stamps is the first sign is an inference not stated.
• sentence 3: support check: partial - Eaton's drained supercap and FIMER's battery replacement appear, but 'usual cause' and the flat-backup-during-outage cause for FIMER aren't stated.
• sentence 7: support check: partial - SNTP use is supported by u4, and u30 warns against changing time since it may overwrite data, but u30 is about Cluster Controller, not a general device claim. -->