Skip to main content

Fun with old school weather displays

Ah the 90's.  Everyone has their own opinions of it, but one of my fondest memories is coming home from school and watching the Weather Channel (this should tell you a little about my school experience).  In particular, I was always mesmerized by  "Local On The 8's"  - a computer generated weather display featuring local conditions, forecast, and radar.

A typical screen of the WS4000 during Local On The 8's
 There was a block of time, twice an hour, during which the output of a machine was featured as TV content.  That machine, was none other than the venerable WeatherStar 4000.

The actual hardware was a rack-mount computer
Cable companies would actually install this at their local head-end, and the Weather Channel would cut to it during designated blocks.  The Weather Channel was actually part network, and part local!  A strange concept.

Well, just when I thought I was a geek, the folks at taiganet.com show me what real geekdom is all about.  Their WS4000 simulator, though a bit finicky to get running, is SPOT ON.  See here:

The simulator is almost indistinguishable from the original, aside from the missing logo.
I had to check it out.  It was better than I could imagine.  It works with real, live data from NOAA and can run continuously in a loop.

However, there are a few caveats to getting this running.  They are:

  • You have to run it on a Windows machine. I have not had any success getting it running on Linux.
  • You must install the Microsoft XNA framework.  This is project was discontinued, and as such won't run on some versions of Windows.  
  • You're graphics card may or may not work. I had no luck getting it to run in a VM (VMware or Virtualbox), most likely for this reason.
After lots of experimentation, I determined that it runs great on a bare-metal Windows implementation running Windows 7 or 8, 64 bit.  

My next urge was to set up a live stream, or "TV channel" that my friends could tune into.  I got it running on a machine with the XSplit Broadcaster, and streamed to a Youtube channel.  I put some copyright-unencumbered music behind it, courtesy of one of my old bands.  The little dream was real.  I decided to pursue improving it.

I dedicated the best "cast-off" laptop that I could - an Intel Core i3 running Windows 8, 64 bit, for a long-term test. It had enough processor power to run both the power-hungry XSplit Broadcaster, the WS4000 simulator, and the music player, with a tiny bit to spare for remote access when I needed to get in.  My first problem was dealing with reboots due to silly automatic Windows updates. Microsoft has no respect for what users might be using their machines for.  After I successfully disabled Windows Update reboots, my channel stayed up for 3 weeks straight. The only reason why there was an interruption was that my Comcast connection dropped for a couple of hours, due to a local outage.

If it's still running (as it is at the time of this blog entry), you can tune in here:


With the experiments showing some success, I want to make things better, and scale up.  It would be great if my friends in other counties could get their local weather data instead of mine.  Since I am doing this in my home, in a tiny server closet, I also have to be conscious of space, power usage, and cost.  I searched around and determined that there was one workhorse that was optimal in these categories, but still probably had enough power to do the job: The 2016 Intel Compute Stick.  With its quad-core Intel Atom processor, and Intel HD graphics, it should be good enough to handle all the tasks required while being small enough to add almost no noticeable impact to my tiny home server closet.  At the time, they were going for around $150, which was kind of pricey if I wanted to build a cluster of them.

Fast forward to last week: Our local Radio Shack was going out of business.  They had a couple of these devices in stock for a little over half-price.  They ship with Windows 10, which I did not have any luck getting the WS4000 simulator to work on - but I figured I would find a way to put Windows 7 on them.  I bought out their stock and came home with two Intel Compute Sticks.  

Turns out that the WS4000 simulator runs great on it, out of the box.  Apparently the Microsoft XNA framework is fine on Windows 10, as long as it's the 32 bit edition (which is what the Compute Sticks ship with)!  So we are off to the races.

The next thing I did was design a miniature "rack" for the Compute Sticks to fit neatly into.  These units actually have cooling fans, so I did have to pay a little attention to thermal design.  Since I plan to run them headless, and since the heat exhausts from a vent opposite the HDMI plug, I came up with a minimalist design of a block with 4 HDMI receptacles.  This allows the exhaust to exit topside, and since heat rises, it will not get into the intake of a neighboring device.  


Two Intel Compute Sticks in my Four-up cluster frame
Time to get configuring, and I will be on the lookout for some more of those quad-core Intel Compute Sticks!  

Comments

Popular posts from this blog

Reaper, Linux, and the Behringer X-Air - Complete Studio Solution, Part 1

Introduction and Rationale This is part one of a major effort to document my experiences with recreating my home studio, entirely using Linux.  Without getting into too many of the specifics, a few months ago I decided that I was unhappy with Windows' shenanigans - to the point that I was ready to make a serious attempt to leave it behind.  For most in this situation, the obvious choice is to switch to Mac OS.  With its proven track record, support, and options for multimedia production, it is naturally the first alternative to consider if your goal is to simply use something other than Windows. For me the choice was not so simple. I despise Mac OS and, in general, the goals and philosophies put forth by Apple in an effort to ostensibly provide users with an "easy" working environment.  It does not help that I have also failed to find any aspect of the Mac OS UI intuitive, but I realize that this is a subjective matter. With my IT background and user-control* favori

An Alternative Take on AI Doom and Gloom

 I've purposely held my tongue until now on commenting about "AI" (or, more specifically as has come to be known, GAN or Generative Adversarial Networks).  It seems like it is very in-style to complain about how it has made a real mess of things, it is displacing jobs, the product it creates lacks soul, it's going to get smart and kill us all, etc. etc.  But I'm not here to do any of that. Rather I am going to remind everyone of how amazing a phenomenon it is to watch a disruptive technology becoming democratized From the time of its (seeming) introduction to the public at large, around November of 2022, to late 2023, the growth and adoption rate has been nothing short of explosive. It features the fastest adoption rate of any new technology ever, by a broad margin.  To give a reference, the adoption rate for AI image and text generation, real-world uses, in just 12 months is comparable to all of that of the another disruptive technology, the World Wide Web, takin

RANT TIME: Why do replies to a message I sent go to my spam folder?

Despite what one would think/hope, sending a message to a given address does not inherently give Google a high confidence that a reply from this address is expected (and, for example, that it should bypass spam checks). I have confirmed with Google's tech support that there is no way to automatically have this happen. The user can do the following: 1. Add the address to your contacts list in Gmail. 2. Check spam folder for replies, and mark it as "not spam" if something ends up there, which should influence the fate of future replies received. I can also approve an address at the domain level, i.e. if it is a big vendor or similar. I've had to do this with several of our Chinese vendors. I regularly ask engineering and purchasing to give me a list of the supplies we deal with, so I can approve them as a preventative measure. For what it's worth, all of the false positive instances of reply -> spam we have experienced have involved the sender's email server