PVBC failing to upload to pvoutput for periods in excess of 30 minutes

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Happens all the time during operation
2.
3.

What is the expected output? What do you see instead?
Uploads occur normally for a period of less than an hour, then no upload for 
next period of thirty or more minutes.

What version of the product are you using (e.g. 1.4.1.9 32bit)?
1.5.0.12 and then 1.6.0.5 both 64 bit.

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

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)
Protocol error. Error: Forbidden 403: Exceeded 60 requests per hour

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.
log attached with trace enabled for first hour.

Original issue reported on code.google.com by r...@rayjones.me.uk on 17 Aug 2011 at 6:50

[GoogleCodeExporter]

Issue 92 has been merged into this issue.

Original comment by DennisMackayFisher on 17 Aug 2011 at 8:41

[GoogleCodeExporter]

Original comment by DennisMackayFisher on 17 Aug 2011 at 8:53

• Changed state: Started

[GoogleCodeExporter]

Can you please upload the csv files for 16/8/2011 and 17/8/2011

Can you also please upload a copy of your SQLite database (pvhistory.s3db)

The logs you posted above indicate that PVBC is seeing constant changes in the 
data already loaded to pvoutput. This is triggering retransmission of datasets 
to pvoutput. This is causing you to hit the 60 / hour limit over and over again.

What type of inverter are you using? It appears to be producing output records 
at varying intervals (based on the log contents). 

Dennis M-F

Original comment by DennisMackayFisher on 18 Aug 2011 at 9:58

[GoogleCodeExporter]

PS

When PVBC reaches the pvoutput limit, you will see no further pvoutput updates 
until after the start of the next hour (quota is refreshed). I believe this 
explains the update delays you reported.

I believe that I can modify PVBC to fix this issue but I want to see tha actual 
data so that I understand the root cause.

Dennis M-F

Original comment by DennisMackayFisher on 18 Aug 2011 at 10:20

[GoogleCodeExporter]

csv files for 16 & 17/8 attached
pvhistory.s3db attached

The inverter is a SB4000TL-20

Original comment by r...@rayjones.me.uk on 18 Aug 2011 at 2:11

[GoogleCodeExporter]

I believe I have found the problem. I am surprised I have not had more 
complaints about this. It looks like an issue that may only affect SQLite 
installs. But most users use SQLite (as far as I can tell). It is a rounding 
issue assocated with the mechanism that tracks whether the value of a datapoint 
at pvoutput matches the current value of that datapoint in PVBC.

I will release 1.6.0.6 with the fix once I have tested it in daylight.

Dennis M-F

Original comment by DennisMackayFisher on 19 Aug 2011 at 10:12

[GoogleCodeExporter]

Maybe other users have not checked that PVBC is doing what they expect, or 
perhaps not confident about reporting an issue. Either way, I'm sure feedback 
is in everybody's interest.
I'll try the next version as soon as you release it, and report back. And 
thanks for the app and all the effort that must have gone into it.

Ray

Original comment by r...@rayjones.me.uk on 19 Aug 2011 at 12:17

[GoogleCodeExporter]

Fixed in version 1.6.0.6

Original comment by DennisMackayFisher on 19 Aug 2011 at 9:48

• Changed state: Fixed

[GoogleCodeExporter]

Please install this version and confirm that it solves the problem. My 
installation uses MySQL not SQLite.

Original comment by DennisMackayFisher on 19 Aug 2011 at 9:50

[GoogleCodeExporter]

Installed this morning and running fine now. No errors in log.
Many thanks.

Original comment by r...@rayjones.me.uk on 20 Aug 2011 at 1:29