Logs time and date flash invalid

[toothy]

Hello All

I'm having a problem with the Logs, the time in the lower center flashes invalid and says 14:46 as the time.  The days seem to flash invalid sometimes also.

When I go to time under misc it says the correct time, it also seems to reset the log to zero Kwh at 14:46 instead of at midnite.

Also in the set-up wizard it won't seem to save my lat-lon, it always seems to reset to around western Washington, it must feel homesick. This isn't really important as I'm using it for wind and sunrise doesn't matter, but may be related, something to do with GMT and the offset, it's about the right differential.

It has been putting out power 11.5 Kwh in the latest day from a 1k rated turbine. The only problem is that at less than 10 degrees that means it is a bit unpleasant out there.

Thanks
Wade

[Halfcrazy]

The current firmware will reset its KWH and stuff once every 24 hours or 2 hours after going to sleep. This was confusing so we now have it resetting at 23:59:59 this keeps everything consistent. We hope to release this firmware sometime this week but it may be next week. The invalid date and time issue is a little odd. One thing is though any data collected before the time was set will have an invalid date and time. Does all the new data show the correct date and time?

As far as the Long/Lat it does remember these in the Classics memory it just does not revert back there when you re run the wizard. This info is currently not used for anything yet anyhow.

Ryan

[boB]

Hi Wade and happy (not TOO happy now) new year !

The Classic actually has two Clocks.   One in the MNGP that is backed up with a coin cell battery
and one in the Classic itself that is not backed up with a battery.  When you set the clock
in the MNGP, it sets the time in the MNGP itself, and when you are in the TIME/DATE set
menu and then press ENTER,  it sends the time to the Classic and sets its clock.
The MNGP also sends the time and date to the Classic after the Classic first powers
up and at other times when the MNGP sees that the date does not match the Classic's
and also once per day, after dusk.

The present MNGP code (that you probably have now) only compares the year but
the next version compares all the time and full date and updates the Classic if different
than the MNGPs time and date.  This compare will only update when the MNGP is in
the main status 1 or status 2 screens at the moment.

Now, to get a bit closer to answering your question about "INVALID" time or date stamp.

When the Classic first powers up, before the MNGP sends it the time and date, the
Classic sets its year to 2003. The lowest year the Classic will allow is 2000 so if for
some reason the Classic gets a bogus time set, it might show up as 2000.  This is
rare but can happen or you could set the time and date to be as low as 2000.

When you see the time or date as "INVALID", all it means is that the year in the Classic
is something earlier than 2011 since 2011 is the earliest year that the Classic and MNGP
time/date has been possible to synchronize.  "INVALID" does not mean that the logging
"data" itself is invalid,  only the time and/or date stamp for that data is invalid.

The quickest way to stop this is to go to the TIME/DATE set menu and press ENTER,
assuming that the time and date is correct in the MNGP.

boB

[toothy]

Thanks for the help

Ryan and boB, the logs look to be correct as far as date for the last week or so, I must have pushed a button then that made it happy. The resetting at 23:59:59 is pretty close to midnite, but mine seems to like 14:46 as it's reset time. I'll do the next few firmware updates and see what happens, 24 hrs is 24 hrs and the wind doesn't rise or set.

The lat/lon is just disconcerting, when the next time you go through the wizard it has jumped from where you left it, you just can't tell if what you entered "took", no worries. Also the Latitude crosshairs move north smoothly until the middle of the gulf of Alaska then jumps to north of Anchorage in one push of the button.

Thanks Again
Wade

[boB]

23:59:59  is being used because  0:0:0   is too close to something that could possibly happen
as the result of some error or reset or something.  Also, 00:00:00 is actually the start of
a new day (MidNite !!)  and and would show up as the next day, so we're changing it to
1 second before midnite.

The Lat/Long should come up approximately where you are located  if you go all the way through the
wizard to the end where it says "Setup complete" and then sends and saves information to the
Classic as well as to the MNGP non-volatile memory.

The way the lat/long was done does only allows the wizard to show up on the map "nearby" where
your location is.  The number in the unit will  (should) be where you left it last time through
the wizard.  The crosshairs come up on the map as opposed to  showing the actual lat/long number.
It's unfortunate it was done that way.  Some day it may be made to come up with the exact location
lat/long number instead of a nearby pixel on the map where it shows up now.

boB