Closed GoogleCodeExporter closed 8 years ago
Re-uploading settings file with database details removed.
Original comment by joshua.h...@gmail.com
on 12 Jul 2011 at 2:03
I noticed re-installing the usb driver put the Envir on a different COM port
(COM6). I changed the COM port to COM 6 and set the baud rate 57600 and am now
getting the attached error log. It looks like a null reference, or object
reference exception.
Oh, I also downloaded the CC test/terminal utility and was successfully able to
connect to COM6 and could see data being logged ~6 seconds so I know the data
is definitely coming through to the pc.
Original comment by joshua.h...@gmail.com
on 12 Jul 2011 at 2:18
Please install version 1.5.0.7. This is the version I use and it contains
significant internal changes around meter menagement. This version matches the
current development codebase and can be easily adjusted if a defect is found.
http://code.google.com/p/pvbeancounter/downloads/list?can=4&q=&colspec=Filename+
Summary+Uploaded+ReleaseDate+Size+DownloadCount
After installation, check "Trace", "Meter Trace" and "Meter Message" on the log
files tab. Save settings and start PVBC.
Dennis M-F
Original comment by DennisMackayFisher
on 12 Jul 2011 at 10:34
Downloaded and isntalled 1.5.0.7 and appear to have the same issue. See
attached for latest log file.
Original comment by joshua.h...@gmail.com
on 13 Jul 2011 at 10:06
Hi Dennis,
Do you have any ideas with regards to the latest log I uploaded? I'd really
love to get this working. I had a look at the pvoutput.org integration service
but would much rather use your solution because it logs to a database first
where as I think the integration service uploads live to pvoutput.org doesn't
it?
Anyhow, do you have any other suggestions as to what I can try to get the
service logging data correctly?
Original comment by joshua.h...@gmail.com
on 15 Jul 2011 at 1:23
The null reference error occurs when PVBC reads 20000 bytes from the CC Meter
port without finding the leading <msg> (start of a message from the meter).
It looks as though the data from the meter is in the wrong character format (no
idea why at this stage). I have prepared 1.5.0.8. This will not give the null
reference error. It should keep running when it cannot find the <msg> entry.
It will dump the mismatched data to the log file if "Meter Message" and "Meter
Trace" are checked.
I am stability testing this version on my own system. I will make it available
when it has been tested for a few hours. Probably tomorrow morning.
Dennis M-F
Original comment by DennisMackayFisher
on 15 Jul 2011 at 6:43
Excellent. I'll test it as soon as it's available.
Cheers,
Joshua
Original comment by joshua.h...@gmail.com
on 15 Jul 2011 at 2:08
1.5.0.8 is available here:
http://code.google.com/p/pvbeancounter/downloads/list?can=4&q=&colspec=Filename+
Summary+Uploaded+ReleaseDate+Size+DownloadCount
Remember to check "Trace", "Meter Message" and "Meter Trace" save settings
before you start the service.
I expect it to produce a large log file very quickly. Be ready to stop it a few
minutes after starting. "Meter Message" and "Meter Trace" are responsible for
the large log file.
Post the log, or a relevant portion of it when you have a result.
Dennis M-F
Original comment by DennisMackayFisher
on 16 Jul 2011 at 12:02
I have tried both Com1 and Com6 but no matter what I do, it appears it cannot
find the <msg> header...
16/07/2011 6:21:55 PM :T9 CC Meter Reader :Converse: DoMessageFind: Not Found:
<msg>
Original comment by joshua.h...@gmail.com
on 16 Jul 2011 at 8:23
One thing I noticed is that it doesn't appear to be transmitting every six
seconds like it is supposed too?
I haven't set the clock on that EnviR unit yet and as it is actually 6:30pm,
the solar has stopped recording anything of note (it still seems to transmit
~30w overnight due to clamp interference?).
Anyhow, you can see there are *some* messages being broadcast on the usb cable
but not many. Do you know what's going on here?
Original comment by joshua.h...@gmail.com
on 16 Jul 2011 at 8:33
Try setting the time. Time must be set correctly to work with PVBC. PVBC relies
on the time being accurate to support 2 hour history correction.
The C2 display shows gaps of up to 2 minutes between messages. This is causing
the timeout in the PVBC logs.
It is possible that you are too far from the CC transmitters. Try moving the CC
display closer to the meter box.
Are the updates ob the CC display at 6 second intervals or are they up to 2
minutes apart?
Dennis
Original comment by DennisMackayFisher
on 16 Jul 2011 at 10:05
It does indeed seem to be an issue related to the time. Once I set the correct
time I could see entries being logged into the meterreading table.
The entries appear to be a bit sporadic. It's not that far away from the
transmitter so I don't think it would have been a signal problem. In terms of
the actual on screen display, it updates every six seconds.
Is there a way to get history data that was stored in the envir unit?
Original comment by joshua.h...@gmail.com
on 16 Jul 2011 at 10:49
The "History Hours" setting determines how much of the 2 hour history is used
to adjust the "Live" data (default is 24). However I suspect any history prior
to setting the time will be unreliable.
If incorrect history adjusts the Live data you can get large numbers of
retransmissions to pvoutput, reaching the hourly limit.
I suggest History Hours should not exceed 24 unless your computer has been off
for a day or more. Set the Tolerance to 5%.
Is it working now?
Dennis M-F
Original comment by DennisMackayFisher
on 16 Jul 2011 at 9:32
I'm not too sure about the history. It hasn't back dated anything (probably
because of the time issue you mentioned). Everything appears to be working
nicely for live data though.
I set the current cost yield threshold to 39w to ignore reported generation
below that (as that is what it tends to sit under over night) but it still
seems to log entries into the database. Also, is there a way to tell the bean
service to ignore entries before say 6am and after 5:30 - 6pm?
I noticed there is a suspend option in there but I don't want to suspend the
computer. Just tell the service to only accept data between those time periods.
Is this what the inverter start/stop is for on the suspend control page?
Lastly, what exactly is the current cost tolerance doing that you mentioned to
set to 5%?
Thanks for all your help.
Original comment by joshua.h...@gmail.com
on 17 Jul 2011 at 6:24
[deleted comment]
You can close this issue now Dennis as you have resolved the initial issue I
was having which turned out to be related to the clock not being set on the
Envir unit (it was on my other EnviR and hence why I hadn't noticed it).
I have everything uploading to pvoutput.org nicely now and have opened a new
issue related to a different problem I am seeing.
Original comment by joshua.h...@gmail.com
on 18 Jul 2011 at 1:59
Original comment by DennisMackayFisher
on 18 Jul 2011 at 10:07
Original issue reported on code.google.com by
joshua.h...@gmail.com
on 12 Jul 2011 at 2:01