Tuesday, November 18, 2014
HAM N00b
Some people may ask, "why the heck would you wanna do that?" Well, there are a few reasons.
For starters, I'm a geek. I'd gone pretty much as far as I wanted to go with photography, and I needed another hobby that would give me reason to read books and absorb information. In comparison to other hobbies, (like say, restoring a car,) amateur radio has some real benefits. It takes up less space. At least, for now. It can (mostly) be done indoors, which is very helpful during the cold winter months. There's less of a chance I'll find myself laying under a car in the mud trying to force stubborn pieces to fit together. And overall, it doesn't cost as much. Again, for now.
Secondly, I like math. And while there's bucketloads of math in everything we do, a lot of it seems to have concentrated itself around radio. And it's the special kind of math, made of imaginary numbers and black magic that makes your head want to turn itself inside out. All of that math boils down to how long to make a certain piece of wire and where to put it so that you can talk to another geek on the other side of the planet. That may sound condescending, but it's not. Geeks are awesome. Without geeks, we wouldn't have cell phones. Or the internet. Which means we wouldn't have Angry Birds or Candy Crush, but it also means we wouldn't have a man-made object drilling holes in a comet.
And then, there's the Zombie Apocalypse. Or ice storms. Or aliens. Or anything else you can think of that can cause a large-scale disruption of the infrastructure that makes civilization work. One of the reasons the government sets aside portions of the radio spectrum for the use of amateur operators is that, given time and geeks being what they are, eventually a communications network springs up that is completely independent of any commercial venture. This comes in handy when those commercial networks fail, such as when a car crash on the highway knocks out a fiber optic cable. Or an ice storm brings down power lines and leaves whole communities without electricity for weeks at a time.
It also comes in handy when someone is lost out in the bush, where there's no cell service and the mountains are too close together to get a signal to a satellite phone. These are places where industry has no need to build a communications network because normally there isn't anyone out there to use it.
For all these reasons, and more, I wrote my test and got my ham license.
Now it's time to start learning.
Wednesday, October 22, 2014
Nothing is simple
Watching this happen, I couldn't believe that the man-machine interface was something as clumsy as a collection of levers and buttons. The movements of the machine were as coordinated as my own arm if I were digging the hole with my bare hands; something I couldn't fully appreciate until I jumped into another machine - a small wheeled loader - in order to move some dirt out of the way.
At one point, he was moving the excavator to a new position, and the machine, deep in the trench, slipped a track. My first though was, "we're screwed." But my brother-in-law, he sends me to fetch a couple prybars. Between those and the winch on the quad, we were able to get the track nearly back into place. And that's when the side of the trench gave way.
Fortunately, it wasn't a complete cave-in. But enough sand sloughed in to bury the track we were trying to wrestle into place. Thoughts of large cranes are going through my head as we head off to the neighbour's to borrow a tow rope.
As I'm rounding up some random bits of chain, my brother-in-law uses the loader to build a shelf that will get the loader close enough to the disabled excavator while keeping it on a firm footing. Then we attach the rope between the two machines. I started the pull on the rope with the loader, which didn't do much.
Until the excavator, using one good track and its only good arm, started crawling out of the pit. I had the image in my head of a wounded soldier crawling out of a trench. The arm would push against the side of the trench, lifting the disabled track off the ground. Then the other track would crawl forward, until the arm reached its limit, and the process would repeat.
Once the machine was on level ground, we attacked the track again with prybars and a small winch. Within ten minutes we had the track back in place and the machine was ready to work again.
That's what years of experience gives does: it takes you from, "All is lost," to "well, shoot, this is gonna set me back a couple hours."
Turns out my coworker was right: nothing is simple.
Thursday, October 9, 2014
One last hurrah: digging the RV out of hibernation
Well, it looks like I jumped the gun on winterizing our new trailer.
By "new", of course, I mean, "New to us". In truth, the trailer is almost as old as I am. However, that doesn't change the fact that it suits our camping needs perfectly, and I couldn't argue with the price.
Where was I? Oh yeah, I got excited about the whole, "I've got a new thing, let's make procedures about it!" thing (is that a thing?) and went ahead and winterized it as soon as I thought we were done camping for the season. Because I take care of my stuff.
Well, turns out that was a less than optimal idea. See, this weekend is Thanksgiving here in Canada, and we're going out of town to visit family. Out of town means securing sleeping arrangements, and with all the other family coming into town, our options are limited.
However, since the snow hasn't flown yet in this neck of the woods, taking the trailer is one of them.
I guess that means I get to try out the dewinterizing procedure!
Thursday, October 11, 2012
The table saw would never be invented today
The other day I was building a frame for a mirror in my house. As part of the process, I had to make some grooves in some dimensional lumber in order to hold the glass in place. To achieve this, I installed a dado blade in my table saw and passed the lumber over. This got me thinking of all the different ways that a table saw could horribly maim someone, and why, if it were invented today, the table saw would never be allowed to be sold.
I mean, it's basically just a blade sticking up out of a table, staring you in the face. Most tools have you placing your hands on the tool to operate it (freehand tools like a chainsaw or circular saw require two hands to keep the tool steady, and a stationary mitre saw is equipped with a deadman's switch so you have to keep one hand on the saw at all times,) but in the case of a table saw, you actually put your hands on the material you're passing through that blade. And unlike tools with a spring-loaded trigger, if you reflexively jump back, the saw just keeps going; the very nature of the way a table saw is used requires the motor to keep running without operator intervention.
So you've got this blade sticking out of a table, whirring away, happy to tear through anything that comes in contact with it. Modern saws have a couple safety devices, but these don't make the saw safe, only safer, and often these safety devices must be deliberately disabled in order to use the table saw to its fullest potential.
Splitter
Blade guard
Anti-kickback teeth
Mediatomb handles my music collection with Mysql
In particular, I'm using MediaTomb to index and stream the media over the network. What's really nice about MediaTomb is that there's no client configuration needed to find the server; the client discovers the server using uPNP. A close second is that MediaTomb uses the inotify facility on the system to detect and index files as they're added to the filesystem. This means that resource-intensive periodic scans of the filesystem are not necessary.
MediaTomb worked really well for streaming videos, but my video collection is rather small. When I tried to index and stream my music collection, it would choke. As it turns out, the default installation of MediaTomb on Debian uses SQLite3 to store the backend database. SQLite, put simply, doesn't scale. I've seen this in other applications as well; I seem to recall trying to deploy Bacula with a SQLite3 backend, with similar catastrophic results.
Anyway, because MediaTomb was trying to use SQLite, the database would get corrupted when trying to add more than a few hundred audio tracks. I tried adding them piecemeal, but it was to no avail; tracks would be missing, or would be in the list, but wouldn't play. Finally I decided it was time to get my hands dirty; MediaTomb will use MySQL, if you tell it to, and I already had a MySQL backend running on my server for other things.
So here's what I did (Thanks to Socrateos for the instructions):
- Start by stopping mediatomb on the server. Then delete the old SQLite3 database, which by default is stored at /var/lib/mediatomb/mediatomb.db
- Edit /etc/mediatomb/config.xml
- Find the <storage> section
- Change "sqlite3 enabled" to "no"
- Change "mysql enabled" to "yes"
- Set the "host", "username" and "password" fields in the mysql section. On my installation, the password attribute was missing, so I created it.
- Save the file and exit
- Next, create a database user:
- $ mysql -u root -p
- mysql> create user 'mediatomb'@'localhost' identified by 'secret';
- mysql> grant all on mediatomb.* to 'mediatomb'@'localhost';
- mysql> quit
- Now create the mysql database...:
- $ mysql -u mediatomb -p
- mysql> create database mediatomb;
- mysql> quit
- ...and populate it
- $ mysql mediatomb -u mediatomb -p < /usr/share/mediatomb/mysql.sql
- Lastly, start the server
- $ sudo /etc/init.d/mediatomb start
Wednesday, May 30, 2012
In Hot Water
![]() |
| The retired water heater element |
Introduction
Why?
Troubleshooting
Parts Acquisition
![]() |
| Air in, water out |
Purging the tank
![]() |
| Now this is a purge kit |
Removing the element
![]() |
| The sediment in the tank |
Clearing the sediment
![]() |
| What I vacuumed out of the tank |
Installing the new element
Testing
![]() |
| Margaritas anyone? |
Flushing
Conclusion
Tuesday, January 3, 2012
On the Science vs the Art
The machine in question is a Kässbohrer PB-140DR. Unfortunately, since it's apparently a rare beast, and I've yet to take any photos of it, I have no pictures to post. I can say, however, that it's basically a smaller version of the grooming machines you see running up and down ski hills everywhere. It's a twin-tracked tractor that has a blade on the front for moving snow, and an implement hitch on the rear that can be used to drag either a packer bar or a hydraulically-powered tiller. Both rear implements have a pair of pans that can be pressed into the snow to set tracks for classic-style cross-country skiing. The result is that the machine can drive over a trail covered in virgin snow, and turn it into a four-metre wide surface that's excellent for classic and skate style skiing, all in one pass.
As the machine passes over the snow, its weight and the cleats on the tracks pack the snow down. However, the tracks leave an unskiable surface. The packer bar is pressed into the snow by the machine; it packs the surface flat, then combs it and presses in one or two tracks for classic skiing.
When the surface is already packed, and the snow has hardened by poor weather, it can be rejuvinated with the tiller. This replaces the packer bar and does all the same things, but it also has a hydraulically-driven toothed shaft that spins at high speed. It rips into the snow and shreds it back into a powder, which is then packed and combed.
This machine is from the 1980's, and unlike more modern machines, is still steered by a pair of control levers in the cab, much like a bulldozer. Having never operated such a machine before, I assumed, probably like most other people, that one would simply grab a lever in each hand and give 'er. However, there are two reasons why this would be a bad decision. Firstly, you need a hand free to operate all the other levers and switches you need to operate while grooming a trail (the levers that move the blade, the knob that adjusts the pressure on the packer bar, the switches that raise and lower the pans and activate the tiller, etc.) because like I said, the machine's from the 1980's; all of the controls are manual. Secondly, the levers are rather sensitive, so it's actually easier to keep control of the machine if you grab both levers in one hand and steer with a twist of the wrist.
I was rather surprised to find that after a morning I'd pretty much gotten the hang of driving the machine down a trail. I was even more surprised to find out that this was just the easiest part, and that I was about to start down the path of learning the art of tracksetting. Things like knowing what effect increasing or reducing the amount of pressure exerted by the packer bar on the snow, or how slow I need to travel while operating the tiller to produce the right consistency of snow. Also keeping an eye on the forecast so that I know whether there's any point in trying to set track (it can't be done when the snow's wet, which can happen from warm weather or rain,) and working out what route to take so that I set the most amount of track the most efficiently (as in not running over trails more than once, since the machine can't be driven over set track without resetting it.)
So this is going to be learning experience for me, but not in the way I'd expected. I started because I wanted to learn to operate a cool piece of machinery, but in the end, I'm going to stick with it becuase it's going to allow me to learn something that can't be codified on paper, something I can only learn through experience.
Now let's just hope the snow sticks around long enough...





