Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Monday, August 11, 2008

Who Needs A Thermostat, Take Three

There is a new application for Google Android platform, AutoHTN, which, among other things, purports to control the home HVAC.

Told ya...

Monday, November 12, 2007

Who Needs A Thermostat?

I've been pondering about this question for a long, long time - starting in about 2001 when the only way to control DZ available was a debug panel, and last time in an essay about SWMBO Compliance Certification (Squeezebox is still a good candidate), but it seems that there's been a new development that might if not put an end to the fruitless search, then significantly widen the options available.

I'm talking about Android.

It remains to be seen how viable the platform is and how many hardware manufactures will jump on the bandwagon. But for now - having worked on different Google APIs (Checkout and Calendar in particular) I can say that it's sure going to be a hell of a fun ride, and I'm about to get busy installing the Android SDK and tinkering with it to see how well can a user interface for a HVAC system work on a cell phone.

Now, who needs a thermostat on the wall, really?

Sunday, August 12, 2007

OUCH! This Is Not Design

This is a kind of engineering I'm trying to avoid: Window A/C Keeps Car Cool.

Feel free to peruse the Digg article for trivial criticism.

Meanwhile, instead of joining the crowd in bashing the guy (totally deserved, I must say) I'll try to be constructive and talk a little about why I claim DZ is not a hack like that.

First of all, two projects (let's call the other one The Window Hack, TWH for short, from now on) solve different tasks, though on surface they may seem to solve the same - inadequate cooling.

TWH is supposed to solve the problem of a HVAC unit, perfectly good by design, but poor by execution, that keeps breaking and sucking money. In other words, it addresses the problem of financial delinquency. With many side effects, not the least of which are the aggravation of outbound cash flow (air drag => $$$ for extra gas) and consumer safety (imagine where that box flies in case of a collision, or if it is simply torn off by the air stream at 70mph).

DZ, on the other hand, is aimed at solving a problem of inadequate HVAC design. Moreover, it solves it in a scalable way that allows to start getting immediate improvements with very little investment, and keep investing into hardware and getting tangible benefits all the way up to the sky.

First of all, you can just install the sensor network and stop right there. Analysis of what you will see may just as well allow you to make adjustments to your home infrastructure in order to bring it to your home comfort requirements.

Then, you can run DZ in passive mode and never touch the HVAC - gives the skittish ones their piece of mind and improvements in home comfort.

Or, you can just go all the way and reap the benefits.

In any case, amount of improvements you get is proportional to your invesment - would it be your time or your money.

Breaking it down to components -

You can start with adding a $10 R/C servo and little labor to get a simplistic motorized register. Like I was saying before, this solution was good enough to work for two years without any necessity to improve it.

Or, you can go for an industrial grade modulating damper - the first Google hit for such a thing that has a price listed puts it at $180.01. I suspect that the actual price will be significantly higher - usually, you have to log in to see the price, and I'm afraid that not everybody would be able to even get an account, it may be restricted to certain audience. Consequently, even that price, whatever it is, is subject to markups all the way up before you are told the final figure.

But if you want to use an industrial grade damper with DZ and can afford it - be my guest, it is not only possible, but accounted for in the system architecture. Oh, and you can have a mixed set of dampers at the same time, so you don't have to spend all that money at the same time.

Same is true for the HVAC unit - DZ can work with a crappy 30 year old HVAC (and, in fact, it did for two years) and allow you to extract significant home comfort improvements even out of that monster. But if you cough up some cash and install a state of art, multistage, variable speed unit (that'll cost you somewhere north of $10,000) - it will happily recognize the features available and will allow you to squeeze even more use out of that.

Bottom line: you get what you paid for. But, you can spend a cent at a time here and there and keep getting returns on what you spend with even minor investments - you don't need to get a loan in the bank to make that happen.

Thursday, August 2, 2007

SketchUp Sketches: DZ Testbed



This is a contraption that can be used to test the zoning controller functionality and operation. As the moment of writing (the image above is live, so is the link) it is just a rough draft (yeah, and it's 2:30AM), but I hope you get the idea. Plug heat sources (electric bulbs will do) into big holes. Plug temperature sensors into small holes. Connect the servos to DZ output. Connect fans to DZ output. Switch it on and watch it go crazy.

Four servos may represent up to four zones.
Four fans may represent up to four HVAC units.
Dimmers may be used to simulate variable heat load.
The divider between two middle fans is missing intentionally.
All sizes in the model (fans, servos, planes) are true and correct.

Link to the model page

Friday, July 20, 2007

Short Take: Fractal Design

For years (I think, starting somewhere in 2000), I've been fighting my delusions of grandeur when explaining the concept of fractal design to people - I thought that obviously somebody must've thought of something this simple way before I did, and, hence, it is a common concept that I heard of somewhere and subliminally decided that I coined the term.

Apparently, not quite. Despite the fact that Google search for fractal design and fractal architecture returns more than enough matches, my patience was exhausted well before I could find anything similar to what I had in mind.

So let me put the stake in the ground, then, and introduce a definition:

Fractal Design: design pattern characterized by approximately same level of complexity at any level of abstraction.

It is a counterpoint to God Object (a.k.a. Blob), Interface Bloat, Spaghetti Code, abused Ravioli Code , Big Ball Of Mud and possibly other Antipatterns.

Starts making sense in context of Complexity Management, which, in turn, is not very well defined in the software engineering domain (this nice essay is just about the only article connecting the two), though, apparently, is widely accepted and practiced in business.

Tuesday, July 10, 2007

Hardware Architecture: Centralized vs. Distributed

Hardware and software are the ying and yang of what modern appliances strive to be. Evolution and oscillations of the software part of DZ is tightly coupled to choices hardware offers.

At all times, cost was the predominant factor. $99 temperature sensor is not a valid choice for someone who is most likely using a mechanical thermostat, but $3 chip probably is.

So what that it doesn't have a nice box - rich and poor are affected by extreme temperatures in strikingly similar ways, and if you can't afford to cover the chip, and you had to staple the cables to the walls instead of paying couple of thousand dollars to the crew that hides them into the walls, so be it. At least, you're comfortable now.

Same goes for professionally installed dampers vs. DIY registers.

So all right, it is clear enough that $3 chip doesn't have a human interface. All the control was initially being provided through the debug console - sure, it was limited to whoever had the password and the inclination to fiddle with it, the rest of the family had it by the way of voicing opinions and complaining (which, surprisingly, ceased pretty soon after the system was activated).

But it is crystal clear that this solution doesn't stand a chance in the long run - in order to pass the SWMBO Compliance Certification, the system must have at least rudimentary controls in each zone (provided the zone is used often enough; it is unlikely that a server room is going to require much intervention often).

Which presents quite a few interesting options.

Rudimentary controls may or may not be terminally dumb.

The dumbest possible control will include a display (two 7-segment LED is just fine) and two buttons (which actually give you more than two possible inputs: you can use "both buttons depressed" as a signal to change the control context). Plain 7-segment LEDs, though, cross the border between "cheap as in inexpensive" and "cheap as in obnoxious" - a graphical LCD won't be that expensive today, especially given the fact that it will constitute just a fraction of the total cost.

Now, what difference does it make if you have two buttons or eight? Granted, two buttons is 4 times cheaper (by themselves), but again, much less so, given the infrastructure considerations: first of all, having 8 soft keys gives you unlimited flexibility for all practical considerations, second, they won't be that much more expensive compared to the total cost.

Does the sensor have to be in the same box as the LCD and the buttons? It depends. First of all, the box has to be located where it is convenient to access it - most probably, next to the light switch. But the sensor has to be located where the actual temperature has to be measured, and that is where the complaining person is - in the bed, at the coach, next to the oven, you name it. On the other hand, the complaining persons lived with a single thermostat for all their life, so even the sensor that is in the box is already going to be an improvement. Another consideration is that this case requires less wiring (assuming it's wired; wireless solutions are a whole different can of worms).

Yet another component is the servo controller. Historically, servo controllers were always centralized - one controller, bunch of wires, servo boosters and capacitors at each servo, good enough.

Later, Nic van der Walt provided schematics for distributed 1-Wire servo controller, which would support bang/bang dampers with no problems at all, and modulating dampers that will be quite noisy - latency of 1-Wire protocol with the bunch of sensors on it is insufficient to provide software controlled quiet transition.

Today, there are chips with PWM supported in hardware, and if they have enough brains to support even the simplest quiet transition possible, then you have the distributed servo controller right there and then.

Considerations above assumed we're ignoring existing 24V dampers (which are mostly bang-bang, and regardless of whether they are or not, they're well beyond the approved spending limit for the audience) and using R/C servos to control the dampers, as shown here.

This just about concludes the story. There are three major topics left uncovered - the HVAC actuators, hardware interface selection, and making all the gadgets wireless - but the article is getting too long, so stay tuned.

Friday, July 6, 2007

Software Architecture: Centralized vs. Distributed

Evolution of software moves in mysterious ways. Especially if you're not the one contemplating it, but the one making it happen. Hindsight is always 20/20, and now that I'm looking back at the way DZ evolved, I'm seeing that I was merely trodding the same path as countless others - namely, coming all the way from monolithic single host software design to modular distributed.

Just as dinosaurs became extinct, DZ ceased to be a monolith even before it become public - the first GPL'd version was already split in several parts able to talk to each other via TCP/IP, and the parts were linked together in a modular container driven architecture.

Further down the road, the project started shedding more pieces as better versions of them arrived elsewhere (scheduler would be one example). It also became clear that as computers become smaller and cheaper, the day will come when it would be not only possible, but beneficial to utilize multiple computers for a task that could be perfectly done by just one - just for the very reason of having a particular computer in a convenient place for connecting hardware.

Most prominent examples would be -

  • An HTPC which has to reside in a rigidly defined place, next to the rest of AV equipment;
  • A wireless router that is a focal point of wireless and Ethernet connectivity;
  • A workstation, which by itself provides several relevant data streams (CPU temperature, motherboard temperature, hard drive temperature).
Which makes distributed communications difficult to underestimate. Initially, it was just about protocols, now, it's getting all about application interoperability and plugins (Cacti, Munin, Nagios, Mister House to name a few).

Stay tuned.

Wednesday, July 4, 2007

The Dual Nightmare

There is an ongoing heated discussion among homeowners and HVAC professionals about what solution to the problem of properly balancing the house is better - zoning the house, or having multiple units installed. There are all kinds of arguments on both sides.

The proponents of zoning are usually saying that it would be silly to use one switch to turn on or off all the lights in the whole house, whereas the opponents are pointing out that it is silly to pump the amount of air intended for all ducts together through one.

The opponents of zoning are usually saying that it is more reliable to have two simple HVAC units than it is to have one complicated HVAC unit and one complicated zoning system, whereas the proponents are pointing out that maybe HVAC professionals may be simply out of their depth and are trying to cover that up by silly arguments.

The opponents of zoning are saying that having two units is an adequate solution to the balancing problem and point out to the fact that existing commercial zoning systems are rarely extending "affordable" options beyond four zones, to which I say they are completely nuts and give the room (read: zone) count for three quite average houses that I've lived in: roughly 11 zones in Iowa farmhouse (2 levels, 4 bedrooms, full basement), 14 zones in one house in Arizona (3 levels, 4 bedrooms, game room, library) and 13 zones in the house I live in now (2 levels, 3 bedrooms). Oh, I do include bathrooms, too.

But I digress.

Sometimes you just have two units - for example, when you simply buy the house with them installed - it would be silly to rip them out, wouldn't it? So one just has to deal with it...

Whereas having two units is certainly nice, it is by no means a guarantee of any improvement whatsoever. Like it was pointed out before, all your luck depends on having the job done right.

Sometimes your luck is improved by the fact that the house was designed with heat exchange physics in mind (little heat transfer between floors, narrow staircases).

Sometimes it is degraded by the fact that aesthetic considerations took priority over common sense - wide open floor plans with walls being mostly glass, rooms spanning several floors vertically, and different floor count in different parts of the house.

Which is exactly the situation I have to deal with right now. The north side of the house (1 floor, 2 rooms + 2 bathrooms) is served by a nice powerful variable speed high SEER Lennox split unit. The south side (2 floors, 4 rooms + bathroom + kitchen + laundry room) is served by a puny rooftop Trane and a set of drinking straws they called ducts.

So let me skip the rant about how unthoughtful that was, and get directly to describing various interactions between two units that may happen. Let's assume for simplicity that we're talking about cooling season behavior.

Unhappy Load Meter

If both units kick in at the same time, and you are on a load controlled electrical billing plan, you're not gonna be happy. Neither is your electrical company, but that's a completely different story for a different time.

Cold Spots

It may happen that both units serve the same room[s], directly or indirectly, and the room has enough or more than enough supply and return capacity, and neither of the thermostats is in it. If both units kick in at the same time, the room will get uncomfortably cold.

Hot Spots

It may happen that the cold air supplied by unit A drags down the temperature at the thermostat controlling unit B. In this case, it will not get unhappy and cause unit B to switch on until unit A is off. Which will cause the rooms normally served by unit B to become uncomfortably hot.

The Skew

To add insult to injury, it is quite possible that the layout described above also makes unit A serve, at least partially, the zone that is supposed to be served by unit B - and in this case, unit A will keep running and running, possibly not even catching up with demand - and it will not get any help from unit B because the effect described above robbed unit B of necessary control input and is preventing it from switching on. You end up with one unit trying to do the work of two, for which it is clearly undersized. To further aggravate the situation, it is possible that the overworked unit will go beyond its normal design range, and then you have a dead unit (ask me how I know).

For more than one floor, The Skew is rather a rule than an exception.

Ask yourself a question, don't you always have to set the thermostat downstairs a couple of degrees lower than upstairs, otherwise it feels hot and stuffy? The scenario above explains it vividly. All there is is a leak of cold air from upstairs through the staircase (or a tall room) that causes the thermostat downstairs to make the unit stay off.

Catch-22

To prevent The Skew (further defined as one of the units working significantly longer than the other), you need to carefully balance the thermostats in such a way that the race never starts. This will usually mean that you will have one of the thermostat set below the comfort level, and the other above. Also, this is going to cost you, because the difference between "comfortable" and "balanced" positions of thermostats is going to make a significant contribution to your electric bill. Also, it robs you of comfort. Also, it will make you fiddle with controls all the time, unless you have monitoring set up, in which case you'll just spend half of the time fiddling.

It would be interesting to know what side of argument described at the beginning of the article you are now...

Tuesday, July 3, 2007

SWMBO Compliance Certification

Weighting the priorities is the most delicate task there is.

On one side, you have a bunch of unhappy people, some of them complaining of being hot, some of being cold.

On the other hand, you have The Other Decision Maker which notifies you in no ambiguous terms that those blue wires on that ivory wall (beautiful combination, if you ask me) won't be tolerated. At least no longer than a week. Or a month. Or a year. Or two.

Depending on how well and how fast you can silence the unhappy gang. You do it fast, you're forgiven.

Until the time when you're not home, but Someone Very Important feels a need to change the setpoint. Right there and then.

Which brings you to the point of explaining that you have to take that remote, press this button five times, that button three times, then... wait, you've just run out of their attention span - one of the kids fell into the pool.

So much for advanced user interfaces.

Squeezebox Black

I'm still toying with the idea to use my Squeezebox, along with a SlimServer plugin, say, xAP for SlimDevices, but by now it is painfully clear that the only person who would be able to ever use that interface, and/or willing to use it, would be me. Though scratch that, I'd probably go directly to web interface. More about that later.

Honeywell T87 Round®

So apparently the Honeywell Round® is still the best thing since sliced bread. Granted, the mechanical one had a drawback that caused the worst kind of thermostat wars: one could swing it all the way up or down in one swift motion, and people on both extremities of the age span could have trouble applying controls in moderation - but it was cheap and simple.

Honeywell CT8775 Round®

And, no matter how badly does a digital thermostat in a round body freaks you out, there are decades of usability research behind it. It solves the task at hand perfectly.

Until you run into something as simple as a heating/cooling schedule. Which shatters your interaction model completely. Not even talking about zoning.

Carrier Infinity control panelHoneywell TH8320

Now, you either have to add more buttons (left), or use soft keys (right). The former solution makes the design more expensive and less durable, the latter makes ergonomics more complicated (but at the same time, more flexible).

In other words, you probably can't get the best of both worlds (simplicity and flexibility) in one package, a compromise is required. Most sensible compromise seems to be in a form of arbitrarily complicated master panel that one has to spend a week programming, and a very few critical functions and overrides exposed to the end user.

To be continued...

Sunday, July 1, 2007

HVAC Interoperability? Forget about it...

"The Home Plug and Play Specification represents a strong first step towards unifying the industry behind a common open industry specification and accelerating the deployment of smart interoperable devices in the home," stated Kevin Kahn, Director of Intel's Communications Architecture Lab and Intel Fellow. "This will enable new applications for the PC bringing increased convenience and security to the homeowner."

This inspiring quotation comes from a press release dated... January 10 1997. Over 10 years ago.

So, what do we have today?

The Home Plug and Play Specification never materialized.
Same is the fate of CEBus, for all practical purposes.
BACnet, Modbus, and LonTalk never made it down to residential applications.

Up to this day, there is no sign of existence of a unified diagnostic interface across residential HVAC devices.

Only the very advanced and recent systems such as Carrier Infinity have remote access, but even for that you have to pay a hefty $100 annual fee, and it does NOT have a simplest possible thing - the Ethernet interface. Yes, instead of providing an ability to plug a CAT-5 cable into it, it goes across the SkyTel pager network, quote, "because it didn't require a computer network to operate".

Side note: forgive me for being blunt, but I don't really understand why two pieces of equipment, both of which reside in my house, keep nagging for money and require a roundtrip across the world, rely on complicated and expensive infrastructure, absolutely refuse to talk to anything that hasn't been paid for and/or thought of by the designers? Two answers come to my mind:

  1. The manufacturers want to milk the customers and make them pay for most number of upgrade modules they can (market segmentation in action, also, see Carrier Infinity vs. Bryant Evolution);
  2. The designers didn't know about the fact that an Ethernet connector hardware costs pennies to implement and the computer network in a strict sense is not even necessary (hint: static IP, DHCP, zeroconf, Ethernet hub).
You pick the answer you like better.


Let me skip the rest of the long list of arguments that lie just beneath the surface, and state the fact as it appears from a consumer standpoint: Interoperability between commercially available hardware appliances is effectively nonexistent.

One of possible reasons for this is that the residential HVAC industry hasn't reached maturity - technically speaking, we're barely at introduction stage yet. None of the manufacturers seem to have realized that with drastically shortened product development and obsolescence it is much more profitable to play nice together than to rip the sandbox apart trying to get the biggest share of toys.

Related is the fact that the explosive growth of IT, achievements in hardware and software interoperability and the benefits they can yield are mostly being ignored.

Yet another fact is that most probably the manufacturers are stuck in the middle of the hardware development pipeline - and they still can't wake up and realize that unless they manage to shake off the illusion that they can pull it off, cut the losses, drop the pipeline and start working as the present day demands, they will be overrun by smaller, more agile companies that are able to utilize all these nice things referred and alleged to above.

Mark my words.

Saturday, June 30, 2007

Imitation is the most sincere form of flattery

Here's a screenshot of a debug console for DZ, published on February 22 2002:




(also, here, here, here, here, and here, and the whole discussion around it here)


Here's a picture of a Honeywell VisionPro Touchscreen Thermostat, released several years later:



Hmm...

Thursday, June 28, 2007

Short take: Insane Complexity

Look, Ma, it's just a light switch...

Reminds me of the first time I went public with the prototype implementation of the zoning thermostat back in February 2002. The question I asked was, "What would be your questions if you saw this thing on the wall in the house you've just bought"? The first answer I got was, What the <censored> is that?

Honestly speaking, the situation hasn't improved much since :)

On the other hand, you've gotta give those designers credit for making something that complicated looking that simple.