Oak had an upgrade this week. It's been running for years with an AMD Athlon XP 2400 on an Asus A7V8X motherboard. With the new tasks of running a 5-disk software RAID5 array and H.264 video codecs added over the past few years, it has started lagging behind. The processor and motherboard have been upgraded to AMD Athlon 64 X2 5400+ Brisbane running at 2.8GHz and 65W, and a Gigabyte GA-M57SLI-S4 motherboard. That should provide something around 2.8x the processing power, more disk I/O capability since the motherboard provides 6 onboard SATA ports instead of the two PCI-to-SATA cards I had been using which would max out at 133MB/s, and I've also quadruped my RAM from 1GB to 4GB.
Instead of upgrading the OS in place, I opted to do a fresh install of Fedora 9 x86_64 onto a software RAID mirror, replacing the old 10-gig non-UDMA IDE system drive that I had been using. This was relatively painless. A fresh mythtv install combined with importing my old database resulted in a working system. I had to copy over my lirc customizations, of course. The on-board sound with the default PulseAudio configuration works fine for everything including the raw digital output for AC3. One quirk I may need to look into is that when skipping around in a AC3 video, there will be an absence of sound for a considerable portion of a second before it comes back. This quirk is better than the problems I've had recently with my (ancient) SoundBlaster Live which would cause the receiver to not switch back to PCM mode on its own after an AC3 stream stopped.
I also upgraded to a GeForce 7300GS-based PCIe graphics card which has allowed me to switch to 'gl' rendering for mplayer, which seems to fix most or all of my frame tearing issues that I would experience when using 1024x768 to drive the TV output.
Still some issues to resolve, and I haven't measured it's power draw yet, but the upgrade process has been a lot less painful than I had feared.
I wasn't impressed with the SG1 franchise's first direct-to-DVD endeavor. I would say The Ark of Truth easily makes the bottom third of SG1 two-parters. Instead of ratcheting up quality or plot, everything became more extreme and intense. Mitchell's lines were more O'Neill-like than ever. Mitchell and the IOA guy were both acting way over-the-top, in a bad way. There was some of the good in SG1 as well, in that some of the issues they had on the ship were of the "let's rethink this" variety instead of the standard Trek plot of "our first idea is great and has no problems whatsoever." But really...
The utter destruction of the Ori makes it worthwhile, provided they don't spend the next movie focusing on the political reconstruction of the ex-Ori universe like they did with the Jaffa. Seriously, I wouldn't put it past them.
Apparently I haven't written anything for a long time. I haven't been doing anything amazing, but here are some events possibly worth mentioning.
I had my four wisdom teeth removed at the end of September. I chose to be Xanex'd instead of having general anesthesia. I'm not a big fan of the idea of being put under, but I liked the idea of not caring what was happening. It's hard to gauge how effective it was, though. I was fairly tense at the start of the operation, but was a bit happier than I maybe should have been for some time afterwards. One notable part of the operation was that I could smell the tooth being drilled apart. I recognized it as the scent of ground bone. I thought it was kind of unique that I recognized it, but I guess a lot of people know that smell. There was less pain and less bleeding afterwards than I was expecting. The 800mg motrin horsepills combined with ice were good for the first two days, and then more typical does of motrin for the next few days kept things mostly painless. I did get the hydrocodone-based prescription filled, but didn't end up using it. Eating was fairly constrained for the first few days but was back to normal shortly thereafter. But at least my dentist doesn't have anything to complain about now.
I bought a truck this past weekend. I had been looking since the beginning of September. A truck has been on the radar for awhile, but finally became actionable. The justification was to get up my driveway in the winter (even after my drive is plowed, it generally takes a few days before the car is able to traverse it) and to haul things (I'm tremendously annoyed that my bike has to be laboriously coaxed into my car even with its front wheel removed). I had been looking at used Ford Rangers and Chevy S10s. The other makes of small pickups seemed far less common. I really didn't like the interior of the S10s. I finally bought a white 2005 Ranger with a good many miles (93k) but at a decent price. Chris had the misfortune of volunteering to drive me to Ephrata to test drive and eventually buy one of two Rangers at a used car dealer. I had decided to keep my car for the time being, and of course during its inspection on Monday, it got new front brakes and needed new tires and is also due for a tune-up. Right now it looks like the truck will be in the garage, and the car will be available for squirrel target practice outside, until the snow comes and they switch places. My current annoyance is that the radio in the truck is almost but not quite 2 DINs in height. I'm not sure that amateur radios are DIN-able anyway, but it would have been nice, if I can ever justify buying a mobile rig.
Warning - long and boring. This is as much for my reference than anything else.
It started Friday - several weeks ago. In the evening, one of my drives, a 250GB SATA, threw some errors. The RAID5 wasn't terribly concerned, it corrected the reads and was happy. There were probably less than a dozen errors, and it didn't kick the drive from the array. I made a note of it, but didn't bother kicking it out manually.
Early Saturday, a 400GB drive dropped out of the array. This drive does this from time to time, going utterly unresponsive but fine upon reboot. I re-added it to the array, and it began to sync up. Chris and I went to the new Circuit City in Chambersburg, as he needed to get a power supply for debugging a box lockup issue. I decided to buy one of those new-fangled DVD burner thingies, as it was probably about time I had one. Upon getting home, my array was not happy. I had 3 active members on a 5 device RAID5. Rebuilding the 400GB had sent the ailing 250GB over the edge, kicking them both out of the array. It's a curious thing to see in /proc/mdstat. The metadevice stayed active, but degraded. Ext3 freaked out and dropped to read-only. I really would have expected the metadevice to deactivate under those conditions... or better yet, be very reluctant to kick a drive from an already degraded array. If only I had kicked the 250GB manually, this would have been a bit less stressful. So, then the contingency planning starts. Do I force the array back together, and try resyncing the 400 again? Will the 250 be so badly corrupted that it makes more sense to force the mostly-current 400 back in the array instead of the 250? Should I dd the 250 to another drive, since dd should at least keep going instead of giving up on the errored sectors? Not pleasant thoughts or options. SMART data was indicating that the temperature of the drive was over 60C--hotter than the box's CPU. I moved it to another machine for diagnostics, which didn't turn up anything. The Hardware_ECC_Recovered was varying rapidly (not that that necessarily means anything...), so I decided it was time to be replaced. I ordered a 500G (WD5000YS) and another Promise SATA-II TX4 PCI card from Newegg. Later that night, I put the 250G back in the box and tried the resync again. I watched the resync all night (something like 4am), waiting for it to either fail, or complete. I wanted to boot the 250G from the array at completion, so this wouldn't happen again. Yes, I could have and should have scripted it. I was worried about my data! The resync completed successfully with no errors. Seems the 250G was much happier after it had flagged its bad sectors.
On Sunday, I really couldn't do anything about the array, so I started down the second storage path of death for the week: the DVD-R drive. I installed it in my desktop, fired up k3b, burned a backup DVD of several years of photos, and it seemed fine. But I could mount it anywhere. Turns out that it (k3b and/or growisofs) wants to burn DVD+Rs as unclosed multi-session discs. Fine. Turned that off, and burned myself another one. It was fine. It was nice to have something work for once.
On Monday evening, feeling lucky from the day before, I tried burning some more photos to DVD, but it was not to be. IDE errors would start spewing into dmesg, growisofs (which had elevated itself to a nice of -20) began consuming the entire machine, making it unusable. I tried different speed settings, just about any option k3b had to offer. I moved the IDE cable to a different controller, tried changing cables, anything... DMA settings, I looked for firmware, but the thing is a no-name OEM drive probably originally from Lite-On, but their firmware won't load on it, and the site supposedly having the firmware genericizer was down. Of course, I gave up at some point and burned something in Windows which was fine... ARRGH!
Tuesday was supposed to be the day of productivity. The new drive and controller arrived, and I installed them. I spent a little time tooling the partition table and began the resync. The mirror resync'd very quickly at 30-40MB/s. The RAID5 resync stayed around 27MB/s when the system was idle, but dropped considerably otherwise. The old setup would only resync around 20MB/s, and was otherwise usable. But at 27MB/s, the system crawled, yet wasn't using up 100% CPU. I think this is the surreal PCI bus exhaustion experience... 27*5=135, and 133 is the maximum for a 33MHZ, 32-bit, PCI bus. But many of my PCI devices (including the northbridge), are 66MHz capable, and from what I've read, 33MHz devices shouldn't be holding back the 66MHz ones entirely, but I couldn't find out how to test/debug this further. Later I found out that the 66MHz-capable bit doesn't mean very much, and what you really need is a 66MHz-capable PCI bus â which mine isn't. Myth wasn't happy about this, as ivtv wasn't getting read from fast enough. The system otherwise felt very sluggish. I left the box up to resync overnight. I fought with the DVD drive some more, too.
Wednesday morning, I checked on the status of the resync. But the box had locked up. I rebooted it and checked the logs. The resync did complete, but sometime later, there was an unhandled interrupt on the IRQ shared between a SATA controller and the video card. Linux then disabled the IRQ, causing all of the drives to fall out incrementally. I brought the box back up, and had to force the array to be "clean" so that it would re-assemble (echo clean > /sys/block/md0/md/array_state ... there appears to be no mdadm equivalent of this action. And you have to write something to the device then for the superblocks to get updated.) I eventually and experimentally determined that running SMART commands on the new 500G drive is what causes the unhandled interrupt. It takes time for the problem to manifest though - maybe it's a race condition somewhere. I haven't found anything in the kernel mailing lists about this, so I will have to research further and maybe post about it.
As far as the DVD drive, I tried different media with equally mixed results. I eventually returned it to Circuit City and bought a better and cheaper Samsung from Newegg. It seems to work much better... no spewing of IDE messages. I almost made myself buy a SATA one, but I didn't want to buy yet another SATA controller and risk more problems with compatibility.
And the 250G seems fine now, so it didn't get tossed either. Sigh.
When I purchased and installed my PVR-500 this fall for MythTV stuff, it had very poor signal quality. I attributed this to my cable provider, and bought a ridiculous +24dB amplifier from WalMart to rectify the problem, which it did. After upgrading the box from Fedora Core 5 to Fedora Core 6, the reception on the box was awful. I confirmed that the change in kernel from 2.6.17 to 2.6.19, or the accompanying changes to the ivtv driver were the cause. After some research, it turns out that I have an "evil" Samsung tuner card, and that in 2.6.17 the internal amplifier on the tuner is not activated by the Video for Linux drivers. So, my original amplifier purchase was to compensate for a software problem. After removing the amplifier (not just turning it off as I had been foolishly trying as a test), the reception was mostly better. Some channels are better than before, but some are worse, and overall I think this was not a good change. However, there is no software setting for enabling/disabling the internal amp (apparently no good reason to turn it off), so I'm going to go with the internal amp instead of maintaining a custom kernel on the box, which is always a pain.
No, probably not. Congress will likely not be able to get much done in its newly elected configuration. And, really, there's nothing wrong with that at the moment. It's not as if either party is interested in what I would like anyway... term limits, bans on consecutive terms, balanced budget requirements, reduced size of government... I really just don't want to hear Nancy Pelosi's voice (or what she has to say), but at the same time, at least we won't have to see Dennis Hastert as often (ouch, sorry).
As far as local races, I would have preferred Casey to have gone against Specter instead of Santorum for one of PA's seats in the US senate. Casey isn't bad necessarily, but I did like Santorum far better. And of course our great governor was re-elected. Rendell does seem to be able to cut some fat in the budget (just not on himself... ouch, sorry, again), but I detest his vast expansion of gambling in the state, as well as his shady ties to our good fiend Comcast. Not that we needed a former football player running the state either...
Overall, it's not great, not good, but not terrible. I reject the maxim that "change is good" as there are clearly counterexamples. However, there's nothing wrong with variety. Two years of a Democrat-controlled Congress after several years of Republican control should make for a healthy competition in 2008.
Vote Libertarian!
The front page of the Shippensburg Sentinel can be summarized by four events from Monday: 3 accidents on the interstate, and one fire. Detouring 81 through Shippensburg is a mess under the best of circumstances, and on Monday, the side streets had to bear the load of an interstate as King Street was closed for the fire.
This morning, however, I found out that Mondays' events had less degrees of separation than I had assumed. Chris (who is in Maryland, at the moment), SMS'd me to say that the woman killed in the only fatal accident was Danielle Forney. Danielle's fiance was Bryan Bender, a good friend of Chris, and more than an acquaintance of mine. We were cabinmates at Rhodes Grove, and Chris occasionally tells me about what Bender is up to. I can't imagine the pain that he is going through. Please keep him in your prayers.
I used to like thinkpads. They were black, IBM tried to be nice about Linux support, and the maintenance docs were readily available online. However, my 600e had 2 issues requiring return for repair, 2 more issues requiring parts replacement after warranty, and then had to be retired due to not working well anymore.
I had thought my R40 was doing better, but perhaps not. A month or so ago I had to replace the hard drive (not entirely blameless here... it was transported frequently with a running drive), and now it seems the video subsystem is beginning to collapse. This morning I noticed some "visual artifacts" that didn't get fixed with a reboot, and aren't a problem with the LCD, as the VGA port shows them as well. So, guess what that means? A new system board. Fun, fun. I'm seriously considering selling the thing as parts and moving to a Dell D410 or D420, or perhaps skipping a personal laptop and using a work laptop. The next laptop will be small and light, that much I know.
Unfortunately, it seems that anything requiring cooperation and coordination is hard to do. I spent the day investigating a likely impossible solution to a problem that doesn't end up needing solved. While at the same time still not having the ability to work on the problem that really needs solved. And no documentation or plan has been given to me other than 3rd party verbal snippets to the overarching project responsible for the whole situation. Sigh.
Luckily, other than this blog, I've been pretty successful at not letting the day ruin my evening. I got to visit with Chris a bit, following his trip to Illinois.
And one more note... recent kernel upgrades for FC5 require a new firmware image for the ipw2200 wireless driver, so remember that.
My great-grandfather's family typically has a reunion on the 4th of July, but for the last few years it has been held on a weekend near that day, and this year it was as well. So, on the 4th, my (less extended) family had a food at my place. We scheduled it for lunchtime, figuring we'd beat the storms predicted, but instead hit them directly. Oh well. I did get to see Discovery launch live on TV, something I've never before had the opportunity to witness. Pretty neat.
This past Saturday we visited with friends of the family over near Shade Gap. Their neighbors put on a professional fireworks show that would put most municipalities to shame (ok, so I'm comparing them to Shippensburg). But it was really quite impressive, and we had front row seats.
There are good networking problems. These are the kind that something happens that you don't understand. You mull over it, eventually diagram out the different layers of the various protocol stacks, and discover that things are working exactly as designed, just not as you expected. Ian and I uncovered an example of this kind of problem a few years back at CTI. There was a periodic surge in broadcast traffic on our LAN destined for a specific box. After ruling out all of the various NAT rules and such going on, we eventually found the simple cause. The box was not sending any packets of its own. So, the switch had no forwarding entry for it. So it did what switches are supposed to do in that case: broadcast the packet. Coming to those kind of conclusions is fun.
There are at least three kinds of bad networking problems. The first is when something is evil by design. An infamous example of this would be the error measurements in the DS1-MIB. Absolutely useless when it comes to making time-series graphs, or setting event thresholds. The design seems to have been one of convenience, since the quantities represented date back to the first of the DS1 channel banks. Anachronistic design sucks.
Another type of evil networking problem is one that is seemingly random. Everyone knows that one of the first steps in troubleshooting is knowing what steps are needed to reproduce the problem. With random events, you're essentially screwed. Turn up the debugging until it gets painful and wait for the event to recur, and pray you captured something useful when and if it does. DDOS attacks and the like can fall into this category, especially for those of us without the ability to do meaningful flow logging. Tracking down random problems is evil.
The third category of networking problems I feel like discussing this evening is the unreasonable problem. This is the non sequitur, the problem that makes you yell futilely at your terminal or coworker, from the complete and utter ridiculousness of it. If you manage to solve one of these, you might end up with a good networking problem, as described above. Or you might want to take a sledge hammer to a piece of hardware. Let's explore some examples:
Near the end of my CTI experience, a certain Astrocom CSU/DSU was observed having a most unlikely problem. If I remember correctly, it somehow would drop packets over a certain size. A most improbable feat considering that your average CSU/DSU should not really have any concept of what a packet is, let alone be able to drop one. Patrick offered a bounty on the problem, but as far as I know, it was never solved.
The last example is the reason I am writing tonight. Last summer at Doug's LAN party, I had difficulties copying large files to my desktop machine. I eventually blamed it on my patch cord, but by that time we were packing things up, so this was never really tested. Even before this, I was having trouble sending large print jobs to my printer. I quickly blamed this on the network card in the printer, or some postscript oddities, but never came to a solution.
Later, when trying to use my desktop as a file server for a CentOS install, I realized that my network issue with my desktop was ongoing. Traffic analysis indicated that during a high speed transfer coming from my desktop to another machine, the connection would stop passing packets. Packets on other TCP connections between the same machines were unaffected, but subsequent retries of packets associated with the dead connection were getting dropped somewhere. Since this seemed to be connection related, firewall settings were verified and found to be fine. I let the problem fester, as it was not causing any day-to-day difficulties, since my desktop isn't ordinarily sending large amounts of data, just receiving.
So, this evening I was talking with Doug about printer stuff, and he made a connection that I had been missing. Was my printer problem related to my network problem? And what about all of those problems with NFS in the recent past? Yes, they all sound like candidates. With that late realization, I delved into the annoying network problem. I replaced the network card. The problem persisted. The cabling was ruled out. And the problem was narrowed down to a switch. A specific switch port, to be precise. Now, I'm not exactly sure how one of my NetGear GS506 gigabit switches is managing to drop packets belonging to a specific connection when that connection begins spouting lots of traffic in a certain direction, but that's exactly what it appears to be doing. And it's reproducible. So yes, a problem as insidious as this problem should be solved with the sledge, but some tape over port 1 of the switch should do. Thanks for the insight, Doug! And if you see a problem like this, check the switch, even though it doesn't make any sense.
That's what's happening. Not Much. I've been moving pieces of dead trees around the house, and have a large stack of wood that needs burned as soon as the County, in its infinite wisdom, ends the burn ban. Also trying to get the shed into a usable condition (which will involve burning a large amount of cardboard at some point).
Other than that, I've been doing some irritating travel for my employer, and it seems that has not ended. And, as Doug mentioned, we won the CVARC fox hunt the other weekend.
The storage capacity upgrade and RAID5-ification has been completed, following a week of computers and their components strewn throughout the house. Having a RAID5 include a linear md as a component was a bit challenging... had to make the kernel not try to assemble the RAID5 automagically, but wait for the mdadm.conf to do it. Unfortunately, that wasn't the end of the computer fun this week. Chris had a drive fail in his firewall, and the machine employeed various means to make it impossible to install an OS on another drive. Still not sure what its problems are, having spent the afternoon in futile efforts to fix it.
[balleman@oak ~]$ df -h /storage
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/storage0-lstorage0
1.5T 739G 729G 51% /storage
My beagle Blazer died last night. He was 14 years old, and had been slowing down over the last few years. We buried him just outside of our woods. It was harder than I thought... I've had him since he was a puppy. I have few friends I've known longer than that.
Blazer didn't move with me when I left home last spring. I knew he would be more comfortable and would get more attention if he stayed home.
My family had adopted a stray beagle mix last spring, naming him Buster. Buster probably kept Blazer better over the last few months, keeping him active. It was also comforting to have Buster to play with today.
"CTI Negativity" had been a term used to describe frustration and irritation with our employer, as well as general foreboding about the future of the company. This condition is beginning to surface at my present place of employment now, too. Some, but not all, of the causes seem to be inverted from the CTI situation. In any case, time once again to start the usual preparatory cycle of discontentment... new job? back to school? try consulting? fix what's broke somehow?
The Democrats outburst of applause at a failure of proposed Bush policy, coupled with Bush's finger-wagging reaction was pretty darn funny last night.
Today, Bob Clay showed me a shirt that says "I see dumb people." That's honestly the funniest thing I've seen this year. I need one of those!
The few weeks from the beginning of the year to the start of the semester were fairly trying, but things are starting to settle down again at work. It does look like I'm required to go for two weeks of Oracle training at some point, which I'm not really looking forward to. The several short training programs I've been through (Breezecom, Hitachi) would have been much better in book form - excepting that neither had good books.
Have you ever noticed that the more time you have available, the less you get done? The short days I think are really making me worthless at the moment. Not much coding on NetMRG and other stuff, with some exceptions. I should be done reading the Hitchhikers Guide to the Galaxy collection before long. Too bad I've been working on it for a year or more.
And it sounds like Chris is learning a bit about the prudence of self-censorship in blogging. The fun thing about the Internet is that anyone can be reading what you write... particularly those you write about! I often wish it were practical to have a blog where only certain people could see certain entries, but that does take some of the fun out of it.
Now, if you'll excuse me, I need to check out this floppy disk I have here labeled 'Shady.'
In case you've missed it, there has been a bunch of fuss lately about a local school district requiring its biology teachers to read a statement on intelligent design to "balance" the teaching of evolution. This went to federal court which decided that such a statement was in violation of the separation of church and state.
This never made sense to me. Evolution describes a "how" of creation - a means by which life as we know it was brought into existence. Intelligent design describes a "why" of creation - meaning rather than means. They are orthogonal topics, without the ability to be contrasted or balanced as the school board allegedly attempted to do. The Dover School Board was nothing short of incompetent in trying to shove these things together. Intelligent design itself might not be a religious endorsement, but its forced usage in this context certainly would seem to be.
There are still things that should be included in a discussion of evolution, though. Irreducible complexity should at least get a footnote. Irreducible complexity is a concept that doesn't intend to disprove evolution, but rather to state that there are still things that cannot be explained completely with current theories. The most important concept that can be taught in science is that science changes, and that no theory is above some measure of criticism and doubt. Science isn't (or shouldn't be) concerned with facts or truths, but with best explanations and predictions of observations. There are probably cases where you should remind your science teachers of this.
In situations like this, extremes get the coverage. There are many that consider the term evolution to be sacrilege when used in any biological sense. There are others that have their hand on the speed dial for their lawyer every time they think God might be inferred in a classroom. Both are stupid. It might be unfortunate, but it's definitely a greyscale world, not black-and-white.
Several years ago, the PA state government began deploying a proprietary trunked communications system... and encouraged County governments to use it. Since it's proprietary, the governments are locked into the price structure of a single vendor (brilliant! bravo!) and radio enthusiasts like me won't be able to use our scanners to listen in (at least, not anytime soon). I'm a big fan of government transparency and openness... and this is moving in totally the wrong direction. All isn't immediately lost however. Even if fire and ambulance dispatch is handled with OpenSky staring on June 1st, 2006 as this article says, it sounds as if paging will still be simulcast on traditional FM frequencies so that voice pagers, sirens, and scanners can function without an upgrade. It seems that radio geeks aren't the only ones concerned... just listen to those fighting fires.
And while I'm ranting... Since this system is IP based, how long will it take before a laptop in a state cop's car contracts a virus because he installed an unauthorized Wifi card, and cripples communications state-wide? Consultants won't go hungry cleaning it up, that's for sure.
No structure here... just some random goings-on:
For the last several kernel updates for FC4, my DVD sharing using GNBD hasn't worked. I guess those special ioctl()s aren't getting translated over or something. And NFS or SMB sharing an encrypted DVD just doesn't do anything good at all (ignoring the fact that NFS seems really sucky with the latest FC4 updates). So, after months of not being able to watch DVDs, I gave up, and bought a USB drive cage to attach a DVD drive to Oak. Works perfectly. Despite performance issues and cabling evilness, I still can't completely rule out a stack of USB drives RAIDed as a bulk storage solution, especially with all of the device mapper coolness in Linux. Too early to be thinking of that, though, as the computer storage fund hasn't matured yet, despite the fact that Oak is at 99% capacity.
As Doug has mentioned, Asterisk and VoIP is still pretty neat. I've setup a teliax account, since they have pricing like nufone with a whole lot of rate centers worth of DIDs (they're essentially a Level3 reseller). So, we just need to get some VPN'ing set up. I'm in desperate need of some UT, and I think VPN might be a useful substitute for a LAN party this winter.
My grandfather (on my Dad's side) has been in the hospital on and off for more than a month now. Currently he has pneumonia, is very weak, and not entirely coherent. Your prayers would be appreciated for what could be a difficult Christmas season for the family.
Things at Ship are going fairly well. I did shoot myself in the foot with the "ip arp inspection" feature of the Sup720 this week though. Does 15 pps of ARP traffic seem like a good default threshold for shutting down trunk ports to you? Me neither. Of course, I asked that question after two ports had been err-disabled. Hopefully Tim and I will get to do a real test of some VMPS soon, too.
Last evening there was a power outage on the Ship campus that left the Computer Center and other buildings without power for a few hours. This was the first time our new UPS had ran until it was dry, and overall we didn't fare too badly. Several major campus buildings, including FSC, Shippen, the Library, and Dauphin, were offline for most of the day. Fortunately power to the few affected residence halls was restored quickly after the initial incident. I fully expect no further class schedule changes as a result of this incident, but as always, this blog is by no means ever an official publication of Ship, so please consult their website or hotline :)
This week I have been playing with my new PRO-2052 scanner. I bought this model because it has an RS-232 interface that can be used to control it. There is a free piece of software, sctl, that allows you to use it in Linux. I have had to tweak the code a bit for my purposes. I needed line buffering enabled to interface sctl with a PHP script, and also had to change the interfacing to make the 'sreport' function work with my model. I'll probably post a patch at some point. So far, I've written a few cheesy scripts to log radio transmissions into a database and play them back. It's not quite perfect, but it is doing what I want. It would be nice if this guy would release his source. I'd love to have the two-tone pager decoder that he has.
I've also been poking around various scanning sites. It looks like there still isn't any progress decoding the OpenSky system used by the state of PA. Apparently it's VoIP based. I also found a site with audio samples of various digital transmission modes. Many of the sounds are familiar from old movies and such. I think the PSK-31 sound is sortof like the bridge ambient sound from Star Trek TOS. Also found a great PDF with lots of communications tone tables, for Motorola Quick Call and others.
One of the things I wanted to take care of this summer was some type of outdoor lighting to be used when coming home at night. There just isn't enough ambient light to figure out how to insert the key into the lock. I was considering LED lighting built into the deck, outdoor lights around the deck, and automating the existing outdoor lighting. Seeing this as an opportunity to finally begin playing with X10, I dove in.
The first phase was to control the deck and garage outside lights with a wireless remote. I purchased some X10 light dimmer switches to replace the light switches, a wireless transceiver, and a remote control. Everything worked well except the remote range seems a bit short. Latency wasn't bad... probably a little less than a second.
Phase two involves the hall light, and a computer interface. I bought a PowerLinc USB and downloaded the WISH / x10dev software. The only "gotcha" for the software was that it assumes your hiddev0 is in /dev/usb whereas mine was in /dev. The error messages were not at all helpful in figuring that out, unfortunately. At this point the interface worked, but I had some phase issues: my two lights were on one phase, and the computer interface was on the other. Instead of building or buying a phase coupler, I went with Doug's suggestion of moving breakers around instead. They're really about the easiest plug-and-play devices in existance, but it was something that I had never done before, so I certainly turned off the mains. My current unresolved issue is that the latency between issuing a command on the computer, and the device receiving the command, is aboud three seconds... way too long, especially if you want to do about six commands for a single event. Still haven't figured out if this is as fast as the interface goes, or if there is a software bottleneck.
So, there's my X10 project summary. I'm pretty happy with the results so far. It's not incredibly cheap (I've spent about $100 to control three lights... albeit with a wireless remote and computer interface), but it has achieved the goal, and now I know a bit about X10 :)
The weather this week has been just great. And I've even had the opportunity to take advantage of it. Sunday, I had a family picnic which I used as an excuse for a rather long hike up and down a mountain.
On Tuesday evening, Chris and I walked a 2.5 mile stretch of the Tuscarora Trail that runs along the top of a mountain. Of course, it got dark, the flashlight wasn't where it was supposed to be, and the return trip was rather interesting. No broken limbs, but lots of scratches and such. This wasn't your nice dirt road kind of trail either - just rocks and the occasional blaze for much of the trail. The cell phone provided a good deal of light towards the end, despite accidentally calling Tim.
On Wednesday, Ian and I hiked (on a trail that was like a dirt road) almost 9 miles. It was pretty dark at the end, but a lot nicer than stumbling over rocks. It was one of the few times I was with Ian this summer, so we had the chance to catch up on all of the happenings since the Spring semester.
Now, Doug's turn should probably be next... but I haven't decided on the appropriate successor to last summer's infamous pipeline hike ;)
I've added the first WAN link to the thtech network: 802.11g to Chris's house. We used garden hose as conduit for about 250' of CAT5e from my shed to the WAP. The WAP was mounted on a pole inside of a tupperware container. Ethernet handled the distance fine, but a trivial POE implementation arrived at by splicing the power adapter that came with the WAP into the CAT5 didn't work. There was too much resistance on the line for the 5v power to overcome. So, we tried stepping up to 12v with a DC-DC converter on the other end. This would result in the WAP partially powering up, but continually rebooting. I figured that this was due to the WAP drawing too much power when it tried to power up the radio. I purchased a higher capacity DC-DC converter at WalMart, and all has been well. We're currently getting 600 KB/s, but earlier tests had us at about 1.1MB/s. We'll have to do some antenna tweaking to try to remedy that.