Record you experience with version 1.7.0 here

[GoogleCodeExporter]

Version 1.7.0.0 is a preview test release. I am keen to obtain feedback as some 
features cannot be fully tested with my facilities.

I am keen to here from: 

Owners with multiple inverters who upload to multiple pvoutput systems.

Owners with multiple inverters on Current Cost meters who upload to multiple 
pvoutput systems.

CMS / Orion / Eaton inverter users - does the new Serial Port handler work / 
improve reliability?

Anyone else who took the time to try this new version and would like to comment

Dennis M-F

Original issue reported on code.google.com by DennisMackayFisher on 4 Sep 2011 at 1:42

[GoogleCodeExporter]

Version 1.7.0.0 uploads incorrect Consumption values to pvoutput. Correct 
values are stored in the PVBC database. Currently working on a fix.

Dennis M-F

Original comment by DennisMackayFisher on 4 Sep 2011 at 9:25

• Changed title: Record you experience with version 1.7.0 here

[GoogleCodeExporter]

Version 1.7.0.1 corrects the Current Cost meter pvoutput upload values. This 
only affected users with Current Cost meters used to record consumption at 
pvoutput.

Dennis M-F

Original comment by DennisMackayFisher on 4 Sep 2011 at 10:38

[GoogleCodeExporter]

How does the Retrieve/Refresh work? Do you have a wiki page for it and the 
other new features? I've just installed the 64 bit version and the application 
hangs then crashes when I click this button. Does the service need to be 
started for this to work?

Original comment by sportsfr...@gmail.com on 5 Sep 2011 at 12:28

[GoogleCodeExporter]

As I pointed out in another issue, when i have ran PVBC, Probably this 
currupted SunniExplorer.sx2 that cannot be running again.
I must Delete SunniExplorer.sx2, and create a new one SunniExplorer.sx2.

The new SunniExplorer.sx2 run for only one time!

 The error is:
 System.FormatException in SMA.Data.Xml.Transformation.XmlTotWhOutItem.Read (XmlReader reader).  String was not recognized as a valid DateTime.

Original comment by stefa...@gmail.com on 5 Sep 2011 at 1:03

[GoogleCodeExporter]

I am preparing Wiki pages for both issues. (Comment 4 has already been dealt 
with via email)

The Inverters tab is only required when you have multiple pvoutput system ids. 
It will crash (being fixed) if you have not established a proper database 
installation. It connects to the database to provide a list of inverters 
detected.

When there are multiple pvoutput systems defined, you can use this panel to 
specify the pvoutput system that is to be used for each inverter. If there is 
only one pvoutput system id, all inverters default to the one available 
pvoutput system.

The list will be empty until PVBC has run and communicated with the inverters 
via the selected inverter manager(s). After the inverter managers identify the 
inverters, you can see them in the inverter list (after a refresh) and specify 
the pvoutput system for each inverter. Upload of yield to pvoutput with 
multiple system ids will only occur after the system ids are allocated to the 
inverters and the settings are saved.

Dennis M-F

Original comment by DennisMackayFisher on 5 Sep 2011 at 1:30

[GoogleCodeExporter]

First new Wiki page is here:
http://code.google.com/p/pvbeancounter/wiki/ConfigureInverters

Dennis M-F

Original comment by DennisMackayFisher on 5 Sep 2011 at 2:13

[GoogleCodeExporter]

Hi Dennis
Tried again this morning and the Retrieve/Refresh still crashes.  I have been 
using an SQL Express database that I previously used.  I have manually edited 
the inverter table in the database to add the siteid which appears to be 
missing.  My configuration is to output one inverter to site 2454 along with 
current cost consumption monitoring, and the other inverter to site 3298.  My 
second system only became live since friday so I am trying to back fill that 
data, will see how it goes. I haven't observed any other issues other than the 
Retrieve/Refresh issue.

Original comment by sportsfr...@gmail.com on 6 Sep 2011 at 1:28

[GoogleCodeExporter]

Note on my comment above - I originally tested on my PC which is 64 bit whilst 
leaving my live system running with the old version of the software (comment 
3).  The issues referred to in Comment 7 are what was experienced running on 
the Win 7 starter 32 bit netbook which is for the live system.

Original comment by sportsfr...@gmail.com on 6 Sep 2011 at 1:59

[GoogleCodeExporter]

Latest update.  Seems ok uploading to first site but can't get any data 
uploaded to second site.  Am noticing the following error message

6/09/2011 8:43:24 PM :T12 PVOutput :PVOutputUtilities: Protocol Error: 
data=,-1,-1 Error: Bad request 400: No statuses added or updated

Have attached log file

Original comment by sportsfr...@gmail.com on 6 Sep 2011 at 11:19

[GoogleCodeExporter]

Version 1.7.0.2 is available now. It addresses the crash than can occur when 
PVBC has trouble loading / refreshing the list on the Inverters Tab.

I found a specific problem with SQL Server databases on my test server when I 
testes this feature. The problem occurs when you are using "Windows 
Authentication" in SQL Server. Windows Authentication uses your personal ID to 
login to SQL Server when you are using the PVBC configuration program (Inverter 
Tab). It uses LOCAL SERVICE as the ID for the PVBC service. These ID's can and 
generally do have different privilege settings in SQL Server. For any SQL 
Server ID to work reliably with PVBC I found it needs the following 
characteristics:

User settings:

Default Database - PVHistory
Default Schema - pvhistory

The ID MUST NOT be a member of the sysadmin security group.

In my case, finding this last setting was the key issue

Dennis M-F

Original comment by DennisMackayFisher on 6 Sep 2011 at 8:24

[GoogleCodeExporter]

Version 1.7.0.2 includes a Database Read Test as the final step in the Setup / 
Check Environment procedure. If a problem is detected, feedback is provided 
about the cause of the problem. This is useful when trying to solve the SQL 
Server refresh problem described in comment 10 above.

I will take a look at Comment 9 today

Dennis M-F

Original comment by DennisMackayFisher on 6 Sep 2011 at 8:29

[GoogleCodeExporter]

Regarding comment 9.

Do you have either Upload Yield or Upload Consumption unchecked on one pvoutput 
system ID. These should normally be checked. I believe the error is related to 
these settings being unchecked.

I will discuss with BB. The -1 entries came from a sugggestion he made 
regarding multiple PC's updating a single pvoutput system id.

Dennis M-F

Original comment by DennisMackayFisher on 6 Sep 2011 at 8:34

[GoogleCodeExporter]

I have reconfigured the SQL Server login as you suggested and the verification 
now works as does the retrieve/refresh button.  The new database read test was 
failing until I got this resolved but it now passes this test.
I do have upload yield checked but not upload consumption.  On restart the same 
message applied so I have reconfigured so that one of the CC meters is 
associated with one site and inverter, and the other CC meter is associated 
with the second site and inverter.  Will see how that goes.

Original comment by sportsfr...@gmail.com on 6 Sep 2011 at 9:58

[GoogleCodeExporter]

Update: It is uploading to both sites with my latter configuration, so there 
seems to be an issue with uploading when yield only is checked.

Original comment by sportsfr...@gmail.com on 6 Sep 2011 at 10:43

[GoogleCodeExporter]

Hi Dennis
I'm observing an error trying to upload data to the second site (sid=3298) such 
that it causes the pvoutput update for this site to stop.  See log file for 
details. 

Also, for the main site (sid=2454) on 2/9 and 4/9 I have two spikes in my data 
that causes the daily yield to be incorrect.  
http://pvoutput.org/intraday.jsp?id=3181&sid=2454&dt=20110904.  It appears to 
be residual from when the two inverters were aggregated.  How can I clear/reset 
this, as the data in the database table outputhistory appears to be correct (is 
this a pvoutput problem not a pvbeancounter problem)?

Jamie

Original comment by sportsfr...@gmail.com on 7 Sep 2011 at 7:23

[GoogleCodeExporter]

For Comment 15

To reload data to pvoutput:

Choose (click on) the pvoutput systemid
Modify "Live Upload Days" until the date to be reloaded is visible in the 
"PVOutput Update Days" date list
Check "Force" on the required reload date in the date list
Go to the day at pvoutput and delete the data for that day from pvoutput
Save PVBC settings
Restart the PVBC service

This will cause the latest data for the Forced day to be reloaded at pvoutput

You did not answer my questions regarding the check boxes. This is important as 
I believe the -1,-1 data values came from one of these being unchecked. I 
cannot see what is happening as I do not know which options are active in PVBC. 
I believe that your configuration REQUIRES that both of these check boxes be 
checked. These check boxes are part of the new feature set and may be causing 
unexpected issues.

Please upload the current settings.xml.

Also, was "Upload Yield" or "Upload Consumption" unchecked when the "Protocol 
Error: data=,-1,-1 Error: Bad request 400" error occurred?

Dennis M-F

Original comment by DennisMackayFisher on 7 Sep 2011 at 10:20

[GoogleCodeExporter]

I just noticed Comment 14 (missed it earlier) so my question regarding check 
boxes is answered. I have found a fault associated with these check boxes. You 
will not be affected if both are checked. I believe this is the case currently.

I will add some trace entries to help isolate the index out of range error. 
1.7.0.3 coming soon

Dennis M-F

Original comment by DennisMackayFisher on 7 Sep 2011 at 10:31

[GoogleCodeExporter]

Hi Dennis
I tried 1.7.0.1 with no luck to my problems with issue 101. my inverter data 
still won't upload to pvoutput. I have just installed 1.7.0.2 to my server and 
will see how that goes tomorrow. 

Thanks 
Shane

Original comment by shaneo3...@gmail.com on 7 Sep 2011 at 11:10

[GoogleCodeExporter]

Version 1.7.0.3 will suit most PVBC users and should be reliable

Version 1.7.0.4 contains changes to resolve an issue with Orion Inverters. This 
change may impact CMS and Eaton inverter users so I am keen to see this tested 
by users who use the CMS Inverter Manager with any brand of Inverter.

Dennis M-F

Original comment by DennisMackayFisher on 10 Sep 2011 at 6:46

[GoogleCodeExporter]

Hi - I have an Eaton Inverter and just tried to run version 1.7.0.4. Please see 
attached snippet from the log file.

After data is read successfully twice, a repeating error occurs. First error as 
follows;

10/09/2011 5:02:02 PM :T5 CMSInverterManager :CMS: ExtractYield - Error in 
'req_data_p1' conversation - timeout

This is followed by the following one minute later;
10/09/2011 5:03:02 PM :T5 CMSInverterManager :Converse: DoMessageFind: Not 
Found: ªª  
 

Many thanks to Dennis for his continuing persistence in trying to solve this 
issue with Eaton inverters

cheers,
Ben.

Original comment by SolarNew...@gmail.com on 10 Sep 2011 at 8:08

[GoogleCodeExporter]

Version 1.7.0.5 has been released. This version (like 1.7.0.4) has changes that 
only impact CMS Inverter Manager users (CMS, Orion, Eaton Inverters). Users of 
SMA Inverters and Current Cost Meters will find no changes in this release.

The changes are:

Extra trace entries (MeterTrace and MeterMessage checked)

Changes to support Orion Inverters (EnergyTotal rather than EnergyToday)

Reset serial port after timeout (attempt to get Eaton inverters working 
correctly)

Dennis M-F

Original comment by DennisMackayFisher on 10 Sep 2011 at 11:12

[GoogleCodeExporter]

Hi Dennis
Re comment 15/17, I am still experiencing regular instances where a site stops 
uploading to pvoutput.  I can't see any extra trace messages for 1.7.0.3.  See 
attached log file. Is there a particular log setting I need to increase.

Original comment by sportsfr...@gmail.com on 12 Sep 2011 at 12:13

[GoogleCodeExporter]

Please check "Trace", "Meter Trace" and "Meter Message" on the Log File tab, 
the save settings. This will produce a large log file so only do this for about 
30 minutes before returning to normal settings. Upload th etesultant lof file.

Dennis M-F

Original comment by DennisMackayFisher on 12 Sep 2011 at 12:25

[GoogleCodeExporter]

Hi Dennis;

I've installed version 1.7.0.5 and looks like the errors persist when 
connecting to the Eaton Inverter. Please see zipped attachment of the log file.

The operating system is Windows 7 Starter 32 bit, and I'm using a Prolific USB 
to Serial adapter to connect the eeePC to the Eaton Inverter's Rs232 port.

This may be an issue with the Prolific adapter, rather than the PVBC software. 
I'd previously installed the adapter on my old laptop running XP, and it 
connected to the Eaton Inverter and read data to the PVBC SQLite database 
without too many issues.

However, the eeePC I'm currently using has Windows 7 Starter, and I remember 
there being some problems when installing the Prolific driver on Windows 7. 
This is a known issue that I eventually solved using an older Proflific driver  
- see forum discussion below;

http://www.sevenforums.com/drivers/4476-prolific-usb-serial-driver-4.html

I've ordered a Comsol usb to rs232 adapter and will retry version 1.7.0.5 of 
PVBC and see if the same errors persist. Will update this discussion thread 
once I've given it a go - unless of course Dennis can spot another problem in 
the attached zip file!

Thanks again,
Ben.

Original comment by SolarNew...@gmail.com on 12 Sep 2011 at 11:22

[GoogleCodeExporter]

Hi Dennis
Log file attached.  I had to run it for a while as the issue doesn't occur 
straight away. You will find that it stops at the following line

13/09/2011 9:58:14 AM :T11 PVOutput/3298 :GenThread.RunThread: Thread stopping 
- PVOutput/3298
Thanks for your assistance.
Jamie

Original comment by sportsfr...@gmail.com on 13 Sep 2011 at 4:06

[GoogleCodeExporter]

Re Comment 25

Can you please upload your settings.xml file

I was surprised to see both pvoutput systems using "RecordConsumption". I need 
to understand that parameters that are in effect.

Dennis M-F

Original comment by DennisMackayFisher on 13 Sep 2011 at 10:09

[GoogleCodeExporter]

xml file attached

Original comment by sportsfr...@gmail.com on 13 Sep 2011 at 11:55

[GoogleCodeExporter]

Re Comment 25

Please try version 1.7.0.6 - it has finer grained exception traps around the 
problem area.

Delete or rename the old log file. Keep the Trace, Meter Trace and Meter 
Message check boxes checked. Save settings and run the servive until the error 
occurs. Please upload the resultant log (as well as the settings.xml file 
requested above).

Dennis M-F

Original comment by DennisMackayFisher on 13 Sep 2011 at 12:05

[GoogleCodeExporter]

Dennis
In relation to your comment about both systems using record consumption, refer 
to my Comment 13 as originally i couldn't get any uploads happening without 
record consumption selected on each system, hence the current configuration.  
Ideally I wish to have inverter 1 with 2 CC meters recording consumption, and 
the second inverter without a consumption display.
Jamie

Original comment by sportsfr...@gmail.com on 13 Sep 2011 at 12:09

[GoogleCodeExporter]

Re Comment 29

Are both inverters connected via Bluetooth / Sunny Explorer?
Why do you need two Current Cost Consumption meters?

Dennis M-F

Original comment by DennisMackayFisher on 13 Sep 2011 at 12:24

[GoogleCodeExporter]

Re Comment 29

There was a defect associated with the Upload Consumption and Upload Yield 
check boxes. This has been fixed. I would prefer to understand the problem with 
you current config before we try a more appropriate combination of settings.

Dennis

Original comment by DennisMackayFisher on 13 Sep 2011 at 12:28

[GoogleCodeExporter]

Dennis

Both inverters are connected via Bluetooth/Sunny Explorer, but one inverter is 
in the shed on a sub board, and the other is in the garage next to the meter.  
The second CC meter is in the shed purely monitoring the consumption there, 
which can't be done back at the main board as the second inverter would be 
exporting here most of the time.  As the inverters are physically separate, I 
have had trouble getting connections to both all of the time, so I'm trying to 
ensure that my bluetooth dongle is operating optimally.  The netbook that is 
doing the monitoring is roughly half way in between at about 10m from each so 
this should be something that I can get stable.
Jamie

Original comment by sportsfr...@gmail.com on 13 Sep 2011 at 12:29

[GoogleCodeExporter]

Has 1.7.0.6 been tried. (Comment 25)

I need to release 1.7.0.7 to address Issue 115

I was hoping to make progress with the dual pvoutput system problem in this 
release

Dennis M-F

Original comment by DennisMackayFisher on 17 Sep 2011 at 11:37

[GoogleCodeExporter]

Upgraded to 1.7.0.7, and data is now being uploaded to output.org, but get an 
error (see Issue 115) when testing from the Basics tab. Not sure why check 
fails, but data is getting there, so happy with that.

Original comment by Windride...@gmail.com on 18 Sep 2011 at 3:38

[GoogleCodeExporter]

Version 1.7.0.8 is now available. It fixes the minor issue with Setup / Check 
Environment. It also fixes a few potential problems that may be affecting new 
PVBC users on version 1.7.0.0 to 1.7.0.7. If you are using 1.7 I recommend you 
upgrade. This is particularly important if you are a new PVBC user (did not 
upgrade froim 1.6 or less).

Dennis M-F

Original comment by DennisMackayFisher on 18 Sep 2011 at 9:02

[GoogleCodeExporter]

Dennis

Re Comment 28.  Attached is the log file.  Apologies for the size, it ran for 
quite a while before failing. I have had to trim it to get it to a manageable 
size.  It fails at approx 12:02am with the line pvoutput.org update stopped.
 Note: I've got issues with my bluetooth so I'm not receiving any generation data from the inverters, but the problem existed previously.
Regards
Jamie
PS. Your wiki on bluetooth issues might help me out.  Just got to find time to 
investigate!

Original comment by sportsfr...@gmail.com on 20 Sep 2011 at 12:21

[GoogleCodeExporter]

Re comment 24:

After substituting the prolific usb to rs232 adapter for a Comsol adapter, 
version 1.7.0.6 of PVBC has been reading data from the Eaton Inverter perfectly 
for 4 days. The original issue therefore appears to be a mismatch between 
windows 7 and prolific drivers, despite the Windows 7 device manager reporting 
no errors with the prolific driver.

My apologies to Dennis.

Cheers, Ben

Original comment by SolarNew...@gmail.com on 20 Sep 2011 at 12:30

[GoogleCodeExporter]

Version 1.7.0.9 is now available

I am hopeful it will address Comment 28

If all goes well this will become the featured release

Dennis M-F

Original comment by DennisMackayFisher on 21 Sep 2011 at 9:21

[GoogleCodeExporter]

Dennis
I have installed version 1.7.0.9 and rebuilt my netbook to address my bluetooth 
issues.  Seems to be working now will need to run for a day or two will advise 
after the weekend if I have any crashes.
Regards
Jamie

Original comment by sportsfr...@gmail.com on 22 Sep 2011 at 5:01

[GoogleCodeExporter]

Dennis

Haven't observed any crashes so 1.7.0.9 is stable from my perspective.

Jamie

Original comment by sportsfr...@gmail.com on 27 Sep 2011 at 1:15

[GoogleCodeExporter]

1.7.0.9 seems very stable. Closing this now.

Many thanks to all who took the time to test this version and assist with 
diagnosis.

Dennis M-F

Original comment by DennisMackayFisher on 2 Oct 2011 at 9:10

• Changed state: Done