Archive for October, 2006

Fixing the leak & TWatch update

The service guy is coming tomorrow to fix the leak that he supposedly fixed the last time he was here. I sure hope he gets it right this time! I just checked how much it has leaked the last few days and it is very little, but it does leak so something has to be done for sure.

Work continues on TWatch, it is seems stable so once I add a bit more error-handling it is time to start adding the fun stuff. The first thing I’m adding is network support – remote viewing.

Legal things

We all know legal stuff is boring, right? EULA’s, CoC’s etc….we all just scroll down the text box to get that “I accept”-button enabled so we can push it whenever we get one of them thrown in our face…

I certainly consider legal stuff boring! But why is it then that I want to write a disclaimer for TWatch? That’s a question I’ve been asking myself for the last few days…I realy don’t *want* to – I just feel I need to.

Any legal-geniuses out there that wants to do it for me? :)

Oh well, time to send a copy of TWatch to a tester!

Lets do it all over again!

Boo! The heat pump is still leaking :( Not much, but it still needs to be fixed. Again. Oh well, it is still functional so I’ve still got heated water and warm radiators….lets just hope it doesn’t totally break down when that huge storm they’ve been talking about on the news hits us…

Some statistics

The user ‘köldmedie’ over at Husdata.se’s forums wanted some statistics for a system with a volume tank….here’s mine for the last five days.

Leak fixed

The repairman came this morning and fixed the leak. Hopefully it’ll work as it should from now on.

It’s leaking!

My dear heat pump is leaking! Time to call the repair-man.
If you look closely, you can even see the drop in that thing to the right in the rightmost image. (click image to view a larger version)

Still working…

…on TWatch, just a bit short on time at the moment.

Logging library and testing

Development continues on TWatch, but in order to accomodate the features I want to implement, I need a logging library. There are a few available, but none of them has the features I want…so I’m writing my own.

If you are interested in testing TWatch, feel free to send a mail to twatch-beta {at} pmalmberg.com (It’s OK to write the mail in Swedish). Not all applicants will be accepted so give a good reason why you should be. Also, the program will be delivered without warranties of any kind so you will use it at your own risk. You’ll need to have .NET 2.0 installed as it is required by the application.

First looks!

Two things:

1) I’ve descided to name the application TWatch ( short for Temperature Watch)
2) It is finally time to reveal the first look of the application. Enjoy!

What you see in the image on the left is the application, with two configured graphs; the upper one with four curves and the lower one with three. Adding another graph is very easy as all that has to be done is to add a <graph>-section to the configuration file.

All available graphs are display under the graphs-menu, as seen in the second image.

Configurable graphs


Here’s an example of how the configuration file might look, resulting in a graph similiar to the image.


<ApplicationSettings>
  <Parsers>
      <Parser>
          <Name>Ute GT2</Name>
          <BasePath>Z:\</BasePath>
          <FileName>Ute GT2.txt</FileName>
          <Start>2006-10-01 23:00</Start>
          <End>Infinite</End>
          <Color>255;0;0</Color>
      </Parser>
      <Parser>
          <Name>Kompressor</Name>
          <BasePath>Z:\</BasePath>
          <FileName>Kompressor.txt</FileName>
          <Start>2006-10-01 23:00</Start>
          <End>Infinite</End>
          <Color>255;0;0</Color>
      </Parser>
  </Parsers>
  <Graphs>
      <Graph>
          <Title>
          My graph test
          </Title>
          <Curves>
              <Curve>Ute GT2</Curve>
              <Curve>Kompressor</Curve>
          </Curves>
      </Graph>
  </Graphs>
</ApplicationSettings>

There are two main secions; Parsers and Graphs. The first one specifies what data shall be available, the second one then tells the application to create a curve-group, based on the specified data. It is possible can have an unlimited number of curves in one graph and an unlimited number of curve-groups. “Unlimited” means within reason, of course.
As can be seen the example, you can specify Infinite as the end date/time. This results in the application parsing all available data, including newly written data. I’m planning on adding several more of these keywords later on to make the graphs dynamic.