Closed GoogleCodeExporter closed 8 years ago
Can you please check the timezone settings in the PV running the PVBC Jet
database.
Has it changed recently?
Original comment by DennisMackayFisher
on 5 Jun 2011 at 8:47
Time zone has not been changed on pc if thats what you mean.
I have not changed times on inverter some days look fine some have bad data.
day one looked ok 1/6 at night that day then next day had 2 sets data one
starting 4am.
Original comment by brett.la...@gmail.com
on 6 Jun 2011 at 6:31
Looked at history file todays power started at 735 am
On pv out 12am to 1220am was making 2600w power then 9am reading start again.
Days total matches inverter . well matches when i take off yesterdays total
20.9kwh added to total power but day total shows 17.
I exported 16.3 gross meter and was home so 17 has to be wrong.
Same another day made 21.9 day total read 17.1 on inverter exported 18.9.
I was thinking this may have some thing to do with it but csv files look ok to
me.
Original comment by brett.la...@gmail.com
on 6 Jun 2011 at 7:19
Please do the following to fix the problem:
Stop the PVBC service
Install this version:
http://code.google.com/p/pvbeancounter/downloads/detail?name=PV%20Bean%20Counter
%20v1.4.2.3%20Setup.msi
Make a backup copy of the PVBC access database
Open the PVBC access database and delete all rows in the "pvoutputlog" table
(this is used to track data sent to pvoutput)
Close the PVBC database
Go to pvoutput and delete all days from 1/6 to today
Open the PVBC configuration and set Live Upload Days to 6 (use 7 if you are
doing this on 7/06/2011 rather than today 6/6/2011)
Uncheck "Force Live Upload" if it is checked
Save your settings and restart the PVBC service
PVBC will proceed to upload the last 6 (7) days of data to pvoutput. The newer
version of PVBC includes some fixes for use with MS Access and uses a new
pvoutput interface that allows more uploads before the hourly update limit is
reached.
Because the volume of data being uploaded, this may take some time to complete.
It will reach the pvoutput hourly limit a number of times. Just let it run it
will eventually process all data. pvoutputlog will be re-populated and normal
operation will resume.
The two graphs seem to be caused by MS Access using UTC (GMT) timezone rather
than Eastern Australia (UTC + 10). I have seen this a few times, always on
systems running MS Access as the database. You will find that the values in the
graph that occurs at night are duplicated during the day 10 hours later.
PVBC does not do any timezone manipulation. It relies on the database to store
and retrieve the data in a consistent timezone.
Please report back your progress.
Dennis M-F
Original comment by DennisMackayFisher
on 6 Jun 2011 at 10:26
Tryed above 6/6 todays reloaded same as before.
Still seems to be an issue.
Thanks
Brett
Original comment by brett.la...@gmail.com
on 6 Jun 2011 at 11:29
noticed error in log days that up loaded
1/6 Missing
2/6 looks fine
3/6 looks fine
4/6 errors 12am readings
5/5 missing
6/6 error 12am readings
Original comment by brett.la...@gmail.com
on 7 Jun 2011 at 6:22
Just noticed todays values no longer going to archive file from inverter.
Went back over past isses we had like allow to run local system .
and ran cacls"C:\PVREcords"/E/T/G"local Service":F Administrators:F.
Still not talking to inverter. Last up grade has effected it in some way.
Original comment by brett.la...@gmail.com
on 7 Jun 2011 at 7:45
This version i down loaded from link. Did not include a zip file of Pvrecords.
Was there ment to be or are old files ok?
Original comment by brett.la...@gmail.com
on 7 Jun 2011 at 10:26
The latest versions setup the PVRecords directory as part of installation. The
required files will be created for you if they do not already exist when you
save settings or click the "Setup / Check Environment" button.
Your existing files and directories will be compatible.
Dennis M-F
Original comment by DennisMackayFisher
on 7 Jun 2011 at 10:34
Cool makes it more simple to install.
Hit check enviroment button passed checks still not getting info from inverter
and log has errors?
Thanks
Brett
Original comment by brett.la...@gmail.com
on 7 Jun 2011 at 10:53
Please upload the error log.
Dennis M-F
Original comment by DennisMackayFisher
on 7 Jun 2011 at 11:02
Original comment by brett.la...@gmail.com
on 7 Jun 2011 at 11:05
The data at pvoutput does not match the data you are trying to load. pvoutput
does not allow you to adjust energy totals down at a point in time, only up.
This is happening for 6/6, 5/6, 4/6 and 1/6.
You need to:
Stop the PVBC service
Delete the data for these days from pvoutput.
Delete all rows from the MS Access database pvoutputlog table for these days.
Restart the PVBC service
This should replace the pvoutput data with the coirrect data from your
database.
pvoutputlog is just a record of the data that has been uploaded to pvoutput.
Deleting the content does not remove actual yield data from your database.
Deleting this data causes PVBC to resend the data. You will get transaction
limit errors but this should be cleared by the morning if youy let it run
overnight.
Dennis M-F
Original comment by DennisMackayFisher
on 7 Jun 2011 at 11:28
This was what we tryed last night . Same result errors 1/6 does not go on 6/6
still has error where access has double inputs 10hrs apart.
Errors is log again.
I stopped pvbc then deleated days in pvoutput.
I then cleared log and restarted
6/6 came back same errors on graph have attached log.
Thanks
Is it worth deleating all info and starting fresh.
System has not read inverter for todays values not in pvrecords file.
Original comment by brett.la...@gmail.com
on 7 Jun 2011 at 11:48
Deleated from pvrecords all dates with errors log has no error now.
Restarted nothing did not read inverter . Coms to inverter ok can see it.
Manual exported 1/6 to 8/6 files to pvrecords . They are still there not in
archive file. Has there been an issue in upgrading pvbc to this new one.
Will attach files
Thanks
Original comment by brett.la...@gmail.com
on 8 Jun 2011 at 10:44
I am going away for two days. I will not be able to work on this until I get
back.
If you agree:
Next Saturday morning please -
1) Stop PVBC and do not restart it (warning it will restart if you reboot the
computer) It may be safer to uninstall PVBC until you reach the restart step
below
2) Upload the settings.xml, PVRecords.log and PVRecords_jet.mdb file
If you agree - I will
Execute PVBC on my computer using your settings and database. I will determine
what is happening and I expect to be able to fix the problem
If / when fixed, I will upload the database file, settings and log files.
You can then
3) Download the database and settings and copy these over the old files.
4) Restart PVBC
Dennis M-F
Original comment by DennisMackayFisher
on 8 Jun 2011 at 11:46
Ok sounds good but first up date
Last 3 days have now worked not sure why but thursday night it started and
worked.
Readings look fine no 10 hour delay or double up readings last few days.
Still errors in log 1/6 5/6 .
These days do not up load to pv output site.
6/6 up loaded and has error 10 hr time issue as before.
One thing i did was with sunny explorer set time to system time this was 6/6
late in day say 9pm.
Before this day total meter on inverter was out day i would make 21 showed as
17 pvoutput showed 21 exported 18+ so 17 was wrong.
pv output readings have been good and day total has been correct after this.
But new pvbc was also installed so could of fixed issue.
I will check for reply if you still want system uninstalled and files uploaded.
log has errors will attach for you to see .
dates with errors are blank on pvoutput site. These errors are dates before new
pvbc installed and time on inverter set to system.
Let me know what you want me to do.
Im not fussed about past days if system keeps working as it is.
Would be nice to have no errors in log.
Thanks
brett
Original comment by brett.la...@gmail.com
on 10 Jun 2011 at 10:31
All data seems to be going on fine looks like problem fixed.
I added missing days. All looks fine .
Thanks for your help on this .
Original comment by brett.la...@gmail.com
on 14 Jun 2011 at 7:24
Original comment by DennisMackayFisher
on 17 Jun 2011 at 11:13
Original issue reported on code.google.com by
brett.la...@gmail.com
on 5 Jun 2011 at 9:49