Current Cost Support Forum

Summer's drawing to a close here in the northern hemisphere, and it raises an interesting question about the collected history data.

Currently, the history aggregates usage into bins for each 2 hour slot. When I set my clock on the CC device back an hour, does that fill a slot with 3 hours of data, or possibly skip a slot, and therefore potentially collects only 1 hour of data depending at the time I change my clock?

How about if I change my clock by a larger amount (say forward 8 hours)?

I think because of those issues and the fact the internal clock is not a good time keeper I would ignore the history from the unit and use a more accurate time source e.g. the connected computer.

Just read the real-time data and ignore the rest and let your application build the historic data from that (with of course more precision).

Automan.

I'm going down that route, but I don't really want to leave my PC on 24 hours a day.

I'm starting to think that what I'll do is use an mBed or an Arduino/Fez micro to capture and process the data myself, and then use it to post to the web somehow.

Of course, that rather limits who we can sell any software we write to, to recoup the investment.

I've just been searching around for netbooks off eBay, etc, because while I've done embedded programming, it may well be cheaper for people to just pick up a ready made device.

I think that might be the best compromise, as they're low power, and I could possibly just leave them on 24 hours a day. I might even find some other things to do with it.

_________________
Seeker
"The Truth is out there!"

Thanks for the useful heads up, Seeker.

Do you actually have 3 phases on your system out there?

_________________
Seeker
"The Truth is out there!"