Going Solar

Earlier this year, I started thinking about whether we should invest in getting solar panels installed on our house. I’d seen a friend, as well as my in-laws, get them installed on their houses, and with our family power bills not being an insignificant cost, it seemed like now was the time to do it. Not to mention taking advantage of the South Australian government’s Solar feed-in scheme

After getting a number of quotes, I chose Solar Depot to supply and install a 4.56 KW system ( 24 x 190W panels) with an Power-One Aurora PVI-4200 inverter.

Because of our roof orientation, they’ve been installed as two lots of 7 panels facing almost due north (see photo), and one group of 10 facing north-east. North is generally best, so the 14 panels should generate most over summer. In winter, however, they’ll be shaded a fair bit of the day by trees, so my plan is for the north-east panels (which won’t suffer shading as much) to pick up the slack. The inverter is able to take the two different voltages and combine them into one output going back to the grid.

A few weeks after the panels were fitted, our new electricity meter got installed. So rather than just watch the dial spin backwards when the sun is shining, we are now selling electricity back to the grid.

The inverter turns out to be reasonably easy to get data out of too. The manufacturer distributes a free application that displays all the generation and running statistics. Physically, it has both USB and RS-485 serial interfaces. The USB sounds convenient, but it turns out that it’s not intended for end-users to use (pity). When I get a chance, it would be great to connect the RS-485 back to my Home Server virtual machine and maybe even write a plugin for Media Center to display our power generation!

This wasn’t a cheap system (our mortgage seems to have taken a bit of a hit over the last few months), but the intention is that all going well, we won’t have any more power bills to worry about for the foreseeable future.

Error deploying TFS Lab - TF259096

I’ve encountered this error a couple of times now:

Environment message: Type=Error; Message=TF259096: Team Foundation Server has stopped the following operation because of an internal error: Deploy environment. Additional information: Sequence contains no matching element.

Try the operation again. If the problem persists, contact your system administrator.

I’d added a new Hyper-V host to SCVMM 2008 R2 and was trying to deploy a lab to the new host. It failed with that error. There’s a good thread in the Microsoft forums that gives the clue as to what’s really going wrong. It turns out that TFS Lab Management doesn’t support clustered Hyper-V hosts. Sometimes “doesn’t support” means “well it might work, but don’t call us if you have problems”. In this case it means “No, it doesn’t work”.

If you run the “Visual Studio Lab Management Health Check” report from the TFS 2010 Best Practise Analyzer (part of the TFS Power Tools), you’ll also get this error highlighted as “Host is part of a host cluseter” (sic).

Removing the clustered host from the TFS configuration isn’t enough. It also needs to be removed from SCVMM too. Having done that, you should be able to deploy again.

Hopefully, this limitation will be removed with TFS v.Next.

Samsung Omnia 7 updated to Windows Phone 7.5

Last night I got notified that the RTM “Mango” update for Windows Phone was available. I’d been running the developer release of Mango for a few months, so there weren’t any huge surprises. One thing that did happen though was some firmware updates from Samsung were also applied.

I’d made a note of the original version numbers so here’s the comparison of what got updated.

Samsung Omnia 7 | Component | Original | “Mango” | | — | — | — | | OS version | 7.0.7392.0 | 7.10.7720.68 | | Firmware revision number | 2424.10.9.13 | 2424.11.8.2 | | Hardware revision number | 3.15.0.4 | 3.15.0.4 | | Radio software version | 2424.10.19.12 | 2424.11.7.2 | | Radio hardware version | 0.0.0.800 | 0.0.0.800 | | Bootloader version | 4.9.2.9 | 5.8.0.5 | | Chip SOC version | 0.36.2.0 | 0.36.2.0 |