Jishar13 / pvbeancounter

Automatically exported from code.google.com/p/pvbeancounter
1 stars 0 forks source link

CurrentCost inverter yield threshold does not always appear to filter correctly #80

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run bean counter and set a yield threshold
2. Note that entries are still logged (and uploaded to pvoutput.org) below the 
yield threshold

What is the expected output?

When, for example I set the yield threshold to 38watts (to offset the the EnviR 
clamp interference) I would expect that this always on 38w would not be 
recorded.

What do you see instead?

These entries being uploaded to pvoutput.org. You might be able to see a few of 
these here well after 6pm when there would be no solar generation; 
http://pvoutput.org/intraday.jsp?id=3564&sid=2779&dt=20110717

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

1.5.0.8 64bit

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

Windows 7 64bit

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

Sql Server 2008

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

See log file for details....but there appears to be protocol errors being 
logged;

17/07/2011 11:23:19 PM :T11 PVOutput Manager :PVOutputUtilities: Protocol 
Error: 
data=20110717,00:20,1,40,0,0;20110717,07:00,17,199,0,0;20110717,07:05,17,199,0,0
;20110717,07:10,34,199,0,0;20110717,07:15,51,199,0,0;20110717,07:20,67,199,0,0;2
0110717,07:25,84,199,0,0;20110717,07:30,101,199,0,0;20110717,07:35,117,199,0,0;2
0110717,07:40,134,199,0,0;20110717,07:45,150,199,0,0;20110717,07:50,167,199,0,0;
20110717,07:55,184,199,0,0;20110717,08:00,200,199,0,0;20110717,08:05,217,199,0,0

Original issue reported on code.google.com by joshua.h...@gmail.com on 18 Jul 2011 at 1:44

GoogleCodeExporter commented 8 years ago
The log shows pvoutput rejecting a total energy update as it does not accept 
energy reductions. I suspect that you set the threshold after data had been 
loaded to pvoutput. This would cause PVBC to report a reduced total energy 
value (all incremental values below 38 watts set to 0).

Because PVBC is constantly trying to update the reduced power values, you 
quickly reach the pvoutput hourly transaction limit (the other error reported).

If you want to reload reduced power values you must:

1 - Delete the full day of data from pvoutput

2 - Check "Force Live Upload" (refer to 
http://code.google.com/p/pvbeancounter/wiki/ConfigurePVOutput )

3 - Set "Live Upload Days" to 1 to reload today, 2 to reload yesterday ...

4 - Save settings and restart PVBC

5 - Always remember to uncheck "Force Live Upload" when the day has been 
reloaded to pvoutput

Dennis M-F

Original comment by DennisMackayFisher on 18 Jul 2011 at 9:13

GoogleCodeExporter commented 8 years ago
Hi Dennis, I am still noticing this even on new data on a new day. It's just 
past midnight now and I noticed on a new day on pvoutput.org with some 
generation after midnight!

I upped the threshold to 41w yet still received a generation at 12:10am of 38w; 
(http://pvoutput.org/intraday.jsp?id=3564&sid=2779&dt=20110720).

Does this sound like a different issue to what you were describing with 
negative data?

Original comment by joshua.h...@gmail.com on 19 Jul 2011 at 2:30

GoogleCodeExporter commented 8 years ago
Please try version 1.5.0.9 (just released)

PVBC uses threashold to manipulate the energy (kwh) not power. Can you confirm 
that it is only power not energy that is non-zero.

Dennis M-F

Original comment by DennisMackayFisher on 26 Jul 2011 at 10:38

GoogleCodeExporter commented 8 years ago
Do you still have issues?

Have you tried 1.5.0.12?

Dennis M-F

Original comment by DennisMackayFisher on 31 Jul 2011 at 7:43

GoogleCodeExporter commented 8 years ago
Hi Dennis,

Sorry I didn't get back to you on this. I have been really busy with work 
lately and haven't had time to come back and check this out or install a new 
version. It doesn't have appeared to have occurred since. Taking another look 
at that pvoutput link I posted above, I can confirm it is just the power and 
not energy that is non-zero.

When I get some time I will update to the latest version and update this issue. 
I'm waiting until I get my new QNAP NAS unit and then I'll setup bean counter 
on that with the latest version (assuming I can compile it on mono).

Thanks for your help.

Original comment by joshua.h...@gmail.com on 1 Aug 2011 at 10:52

GoogleCodeExporter commented 8 years ago

Original comment by DennisMackayFisher on 14 Aug 2011 at 6:59