Erroneous data in pvoutputlog table

[GoogleCodeExporter]

What steps will reproduce the problem?
1. steps unknown
2.
3.

What is the expected output? What do you see instead?
At the beginning of some days (happened on 12 & 14 September) erroneous data is 
being  added to the pvoutputlog table that is not in the outputhistory table. 
This data then displays on pvoutput.org. The erroneous data is added starting 
from midnight. When the system starts collecting data from the inverter the 
data is zeroed again so it appears in the pvoutput chart as a spike at the 
beginning of the day.

What version of the product are you using (e.g. 1.4.1.9 32bit)?
1.6.0.6

What Operating system (XP, Vista, Windows 7 - 32bit or 64bit)?
Windows 7, 32bit

Which Database Type (MySQL, MS Access, SQLite - If Access, 32bit or 64bit)?
SQLite

Are there any unusual messages in PVService.log? (upload a copy to this
issue if there are) No

Please upload your settings.xml file with the issue. This answers many
questions I would otherwise need to ask.

Please provide any additional information below.

Original issue reported on code.google.com by acm...@gmail.com on 14 Sep 2011 at 11:56

[GoogleCodeExporter]

Investigating

Original comment by DennisMackayFisher on 14 Sep 2011 at 8:55

• Changed state: Accepted

[GoogleCodeExporter]

The values that appeared on the two days are not random. They are a 20 minute 
and 25 minute period of real data shifted by 6.5 hours. You will find the data 
series repeated at 8:30am each day.

The PVBC Sunny Explorer Inverter Manager replaces the entire day in the 
outputhistory table whenever a .csv file is processed. This means that evidence 
of a problem can be erased from outputhistory.

pvoutputlog is updated by individual row. The non zero 5 minute values 
calculated from outputhistory are compared with the appropriate 5 minute entry 
in pvoutputlog. The row is updated and marked for pvoutput upload when a 
difference is found.

The 5 minute values in the early morning will not be detected by this process 
if there is no non-zero data for that interval in outputhistory.

I have seen pvoutput reject data uploads that cause the total energy for the 
day to be reduced at a point in time. This is present in your datasets so I am 
unsure of how the data was loaded. pvoutput also has "Moon Powered" errors that 
sometimes appear when PV generation occurs at night. Perhaps these restrictions 
have been relaxed or do not apply in the batch uploads used by PVBC.

The PVBC "Force" option does not remove entries from pvoutputlog, it only marks 
them for fresh upload. I will include an option to fix this pvoutputlog data 
issue in the next release.

The only immediate solution involves:

Manually delete the invalid rows from pvoutputlog (this will be the sunject of 
the fix)

Manually delete the bad days from pvoutput.org (you pvoutput login allows you 
to do this) 

Check "Force" on the invalid days on the pvoutput tab (you may need to increase 
Live Upload Days to get access to the day) and save settings

Restart the PVBC Service. The restart must occur soon after the Force entry is 
set as this setting is time limited (no more than 10 minutes).

What caused the problem?

I have seen similar issues when the time (or time zone) of the computer is 
changed. 
Or if the time in the inverter is adjusted. Sunny Explorer can adjust the 
inverter time to match the computer time. I am not sure when or how often it 
does this.

Dennis M-F

Original comment by DennisMackayFisher on 16 Sep 2011 at 11:59

[GoogleCodeExporter]

Closing this now

Post again if you have further trouble

Original comment by DennisMackayFisher on 21 Sep 2011 at 10:01

• Changed state: WontFix
• Added labels: Type-Setup
• Removed labels: Type-Defect