A New Computer

The end of a rough month brings a nice reward.

I’d been thinking about replacing my aging 24-inch iMac computer with a newer, faster model for some time. I almost did it in April, but some Twitter friends wisely advised me to wait for the new models, which were due out in May. By that time, I was hard at work on My Mac OS X Lion book, racing against a deadline set not only by the software’s pending release but by my annual trip to Washington State for cherry drying work. I didn’t get the book done before I had to leave, so I packed up my iMac and other office equipment and headed north. I decided to wait until I was finished with the book. If I had a computer sitting there, waiting for me to set it up, I’d be too distracted to get any work done.

Death of a[nother] Hard Disk

Not buying the new computer turned out to be a bad decision. On Friday, June 17, the iMac gave me a weird error message about ejecting a disk — when I hadn’t ejected a disk. I was running out the door to take care of other business and when my computer wouldn’t shut down the usual way, I just powered it off. Later that day, it wouldn’t start from its internal hard disk.

That’s when I started to realize I might have a problem.

I knew I had a problem the next day when Disk Utility — the Mac software that can usually fix disk and directory related problems — couldn’t fix the disk.

My last full backup had been in May. I use Time Machine for effortless backup, but I’d disconnected the backup drive when I left home. Although I didn’t bring the drive with me last year, I did bring it this year. I’d been thinking about hooking it back up, but laziness got the best of me. So my most recent backup was about three weeks old.

Since then, I’d written at least a dozen chapters of my book.

I was lucky. Really lucky. I was able to mount the disk and suck important documents off it — including those all-important manuscript files. I also sucked off the applications, which had not been backed up. With my most important files on an external hard disk and the big Time Machine backup handy, I tried to format the hard disk, figuring I’d reinstall the software I needed to finish up the book.

My luck didn’t hold. The hard disk just wouldn’t consistently mount. I couldn’t successfully reinstall the operating system on it. It looked as if it needed a new hard disk. Again.

A Temporary Solution

So now I had a book project due very soon that required a working computer with a big monitor to complete. After all, I do layout for my Visual QuickStart Guide books and I shudder to think of laying out a book in InDesign on a 13-in MacBook Pro.

I stayed amazingly calm. First, I hopped into the truck and went to Wenatchee. At Costco, I bought yet another portable WD 1TB USB hard disk.

Yes, I know FireWire would be faster, but it isn’t as if Wenatchee, WA has a lot of choices when it comes to computer hardware. Besides, rain was moving in and there was a good chance I’d need to fly. I didn’t have time to look for a better option.

A new internal hard disk was out of the question. Special tools and expertise is required to disassemble an iMac and install a hard disk. I lacked both.

So I set up a USB hard disk with Snow Leopard, Photoshop, and InDesign. I had the original discs with me, since I planned to do a clean install on my new computer when I got it. I didn’t even bother updating any of them. I just got back to work.

And I was surprised. I expected the computer to be painfully slow. After all, it was booting from an external USB 2 hard disk. It was running some pretty intense software from the same disk. Although I saw a spinning beach ball a lot more often than I like to, it was tolerable.

The New Computer

Of course, while all that software was installing, I was on my laptop, configuring the computer’s replacement. I ordered a very sweet system:

    27" iMac

  • Computer Model: 27-inch iMac – the monitor size is 3 inches larger than my old computer, but it’s widescreen instead of standard so it really doesn’t seem that much bigger.
  • Processor: 3.4GHz Quad-Core Intel Core i7 – this is the best and fastest processor offered for this computer. The Apple sales guy told me that it was faster than current Mac Pro models. (Of course, those are due to be updated shortly.)
  • RAM: 8GB 1333MHz DDR3 SDRAM (2x4GB) – this is twice as much RAM as I had. And the configuration will allow me to double it in the future because there are 4 RAM slots and I’m only using two.
  • Hard Drives: 1TB Serial ATA Drive + 256GB SSD – yes, that’s two hard disks to destroy.
  • Graphics: AMD Radeon HD 6970M 2GB GDDR5 – this is the best offered. I figured it would come in handy for my video editing work.
  • Mouse: Apple Mouse – call me old-fashioned, but I don’t like to depend on battery power for a mouse. Besides, already I have all kinds of Bluetooth pointing devices I had to buy to write about.
  • Keyboard: Apple Num Keyboard – I don’t like to depend on batteries for a keyboard, either. I do have a Bluetooth keyboard if I decide I want to use it.

The computer cost a small fortune. I get a minuscule discount from Apple as a Peachpit author; it was almost enough to cover sales tax. But I can justify the expense. I use my desktop computer for so many things in all of my business endeavors, from writing and laying out books to processing video to invoicing and accounting to creating marketing materials. Why settle for less than the best (if you can afford it) when the best can make you more productive?

It took nine days for the computer to arrive. It was shipped via FedEx directly from China. (I sure do wish Apple and other companies would build things here.) It was delivered to my RV in Quincy, WA, where I’m living for the summer, the day I finished writing the book. It sat in its box overnight as I finished up a bunch of editing.

There was no unboxing ceremony. I deactivated Photoshop and InDesign on my old iMac and shut it down. I moved it from desk to countertop, wiped down the desk, and set up the new computer.

I know this is going to make me sound like an Apple fan-girl, but as I took the crystal clear cellophane off the monitor, I couldn’t help but think how beautiful the computer was. And, as I thought about it, I realized how incredibly weird that was. Hell, it’s just a computer.

Setting Up

My Hard DisksBecause the computer had two internal hard disks, I decided to get a bit fancy with the setup. I left the operating system and applications on the smaller SSD drive and moved my Home folder to the larger ATA drive. I didn’t just put my home folder on that drive. I made my home folder the drive itself. Not only does the disk icon look like a Home folder icon, but when you open it, you find the contents of my Home folder. One less level of folders to dig through.

As for hard disk names, I always try to give my disks meaningful names. Now I had two disks to name. It was quite a dilemma for me. I put it to my Twitter friends and @BrianDunning came up with an interesting suggestion: Cyclic and Collective. At first, I didn’t think they were quite right. But the names grew on me and I wound up using them.

I spent most of yesterday installing software from original program disks and downloads from the Internet. My Internet connection here is via MyFi with a 3 GB monthly bandwidth cap. (I’ve already hit 6 GB this month; that’ll cost me an extra $30.) So I did most of my downloading from a coffee shop yesterday morning and from a wine bar yesterday afternoon. Microsoft Office 2011 was contained in a 1 GB file; other updaters were nearly as large. Had a hiccup with my Final Cut Pro installation and had to restart it; sure hope it works this time because it seems to take forever.

As for Time Machine, I also bought a Seagate 2TB desktop hard drive at Costco. I set that up to back up both drives. I plan on getting some mirroring software to mirror each disk on portable drives. That’ll be a total of two full backups. Lesson learned.

I have some final editing to do on my book and I expect to get to that this afternoon. I’m sure it’ll take quite a while to get the new computer set up the way I need it to. But I’m looking forward to the process and having a clean installation of software and files on a much faster computer.

Juggling Internet Bandwidth

Working with bandwidth limitations.

This summer, I’m on the road again, working out of my RV, the “mobile mansion.” And, after dealing with crappy, overpriced Internet service at my first stop for the past three years, I decided to go it alone this year with a My-Fi.

Why My-Fi?

My-FiThe reason I picked the My-Fi (instead of setting up a mobile hotspot from my smartphone) was twofold:

  • The My-Fi unit came with better plans. There was a 3GB plan for $35 which would only cost $10/GB if I went over. I knew I’d likely go over at least a few times a year — last summer, I had an 8GB month. The other plans would have been far more costly for that overage.
  • I’m a Verizon customer and I wanted to be able to talk on the phone while using the Internet. I admit this was not a primary concern. Last year I used mobile broadband tethering from my BlackBerry and did occasionally get interrupted by a phone call while doing my Internet thing. It didn’t kill me to wait until I was done talking. After all, I spend very little time actually talking on my phone.

I should note here that I do know that the Virgin Mobile My-Fi has a plan with unlimited bandwidth. But what good is a device that doesn’t work where you are? The Virgin Mobile device doesn’t have coverage in the areas I travel to. Verizon does. That’s the same reason — or one of them, anyway — why I don’t have AT&T.

My Plans

Last summer, I was spoiled. Although I paid for Internet at my first stop, I also had free unlimited Internet access through my BlackBerry. I’d had tethering for years and was grandfathered in on a plan that offered unlimited bandwidth for only $15/month. That plan was not available for either iPhones or Android phones and I needed a step up from my BlackBerry. Turning off that plan was one of the hardest things I ever did as a techie.

Of course, my iPhone and iPad also have 3G coverage, giving me access to the Internet from either device without a Wi-Fi (or My-Fi) connection. The iPhone’s plan has unlimited 3G, which is nice. But I’ll be the first to admit that the last device I want to surf the Web with is a smartphone. For the iPad, I went with a limited plan offering only 1GB per month. The idea was that I’d do my heavy Internet lifting with my desktop or laptop computer and limit the iPad’s use to reading RSS feeds, doing a little Web surfing, and sending the odd e-mail.

My goal, of course, is to not go over any bandwidth limitations for the entire summer. And that seriously changes the way I access the Internet.

For example, right now my My-Fi is turned on and ready to access. But the AirPort (or Wi-Fi) connectivity on my computer is turned off. Why? Because my computer seems to access the Internet any time it can, sucking down my bandwidth for no apparent reason. No, I don’t have a virus or worm. But my computer does like to check in with the various services I use — MobileMe, DropBox, etc. — to see whether it should download any updates or get any files. It does anytime it’s connected. While I could disable a lot of these automatic checks, it’s a lot easier to just turn off Wi-Fi until I actually need it.

SurplusMeter

SurplusMeterYou might be wondering how I know what my computer is doing. Last summer, I picked up a Mac app called SurplusMeter. It’s kind of neat. You set it up, tell it how much monthly bandwidth you have, and what day the month starts on. You also tell it how you’re connected to the Internet. It calculates a daily allowance; the idea being that if you use less than your daily allowance, you have a surplus to use during the rest of the month. Then it runs in the background, monitoring your network access. You can launch the app at any time to see what your totals are. Here’s mine for this month, which started just a few days ago. Last night, I was in the red, so even though it’s early, today’s allocation has been partially consumed.

Now, of course, I can use as much Internet as I want per day. The idea is for the monthly total to be less than — or, ideally, exactly — 3GB. SurplusMeter helps me rein in my Internet usage so I can minimize it.

Two things to note about SurplusMeter:

  • I’m only running it on one computer. That means it’s only logging bandwidth usage on one of the four computers I have with me. (Don’t ask.) Laptop access is not being logged. This results in an understatement of total usage.
  • It logs all AirPort activity, including local network activity. That means that every time one computer talks to another — for example, to share files — that usage is also logged. This results in an overstatement of total usage.

I’m hoping these two discrepancies net each other out.

And no, it isn’t worth it to set up multiple copies and use some other file transfer method to get more precise information. All I’m interested in is ballpark numbers.

But if you do know of a better app for the task that doesn’t cost a fortune, please do let us know about it in comments.

Getting the Big Fat Files

Of course, I still have to access the Internet for things that would make a serious dent in my allowance. For example, right now I’m working on a Mac OS X 10.7 Lion book. The Developer Previews I’m using as I write are about 4GB in size. There are two problems with this, and both are pretty obvious:

  • Downloading a 4GB file over a My-Fi with a max download speed of about 1Mbps would take more than 10 hours.
  • If my monthly allowance was only 3GB, I’d exceed that with just one download.

Fortunately, I’m running Lion on a laptop. Over the years, I’ve identified some Wi-Fi hotspots with pretty fast download speeds. One is in Wenatchee, at a coffee shop, where I was able to download a 900MB file last summer in less than 12 minutes. There’s a gas station in Quincy that used to have pretty quick Wi-Fi, although I admit I haven’t tried it yet this year. And there’s a coffee shop in Quincy that might have decent speed; the only time I used it, speed was not a concern. I do know that the local library’s Internet absolutely sucks, so it’s not likely that I’ll be using it for Internet access anytime in the future.

Yesterday, while in Wenatchee, I used the coffee shop Internet to download podcasts, check for updates, get maps for ForeFlight on my iPad, and do whatever I could. If I’d stayed in Wenatchee a few more hours, I would have gotten the big file I need today. I figure I’ll try the Quincy coffee shop first and if that isn’t fast enough, I’ll try the gas station. If that’s not fast enough, it’s another trip into Wenatchee for coffee and a high-speed Internet fix.

Doing Chores with iPhone

In the meantime, I’ve been trying to use my iPhone as much as possible for small tasks such as checking e-mail and sending/receiving Twitter tweets. After all, there’s no bandwidth cap, so it just makes sense to maximize usage. For some reason, I’ve been getting a ton of spam lately — 10-20 messages a day about dieting or “male enhancement” — and it’s quick and easy to just delete these from my phone so neither my iPad nor my computers need to retrieve them.

I know this is a drop in the bucket as far as Internet usage goes, but the way I see it, every little bit helps.

Rising to the Challenge

This summer is an experiment to see how well I can limit my usage and stay within budget. I’m prepared to pay for the extra bandwidth, but I like the challenge of working within limitations. It’s a lot like trying to conserve energy by turning off lights and turning down the heat/air conditioning.

It’ll be interesting to see how I do.

Dangerous Flying: Abrupt Control Inputs

How sloppy flying could get you killed.

Recently, while flying with a 200-hour helicopter pilot, I was startled when he rather abruptly shifted the cyclic to make a turn. I didn’t say anything then because it wasn’t too abrupt (whatever that means). But when he did it again later in the flight with an even more abrupt movement, I spoke up and told him not to do it again.

Understand that we were flying a Robinson R44 Raven II, which has a rather unforgiving semi-rigid rotor system and very long rotor blades. We’re taught — or should be taught — during primary training to use smooth control inputs, especially when working with the cyclic.

I’m not a CFI and I don’t feel that I have the right to tell someone how to fly, but when a pilot does something I believe is dangerous, it’s my duty to speak up. So I did.

The trouble is, I’m not sure if he believes what I told him — that abrupt inputs are dangerous — or if he thinks I was just nitpicking his technique. (I let it go the first time partially because I didn’t want to be seen as a nitpicker.) Since so many pilots seem to read this blog to learn — or at least to get my opinions on things — I thought I’d discuss it here.

What Robinson Says

Section 10 of the R44 II Pilot’s Operating Handbook includes safety tips. Here’s the one that applies:

Avoid abrupt control inputs or accelerated maneuvers, particularly at high speed. These produce high fatigue loads in the dynamic components and could cause a premature and catastrophic failure of a critical component.

What Robinson is saying is that when you make abrupt control inputs you put stress on various aircraft components. They’re likely concerned about the rotor blades, mast, transmission, and control linkages most. This makes perfect sense.

Robinson Safety Notice SN-20, titled “Beware of Demonstration or Initial Training Flights,” includes these statements:

If a student begins to lose control of the aircraft, an experienced fight instructor can easily regain control provided the student does not make any large or abrupt control movements. If, however, the student becomes momentarily confused and makes a sudden large control input in the wrong direction, even the most experienced instructor may not be able to recover control.

And:

Before allowing someone to touch the controls of the aircraft, they must be thoroughly indoctrinated concerning the extreme sensitivity of the controls in a light helicopter. They must be firmly instructed to never make a large or sudden movement with the controls.

Of course, what worries Robinson here is that student pilots may make erroneous control inputs beyond what an instructor can fix to regain control of the aircraft.

What Worries Me More

January 31, 2012 note: Since writing this, a friend on the Rotorspace site has brought the topic of Mast Rocking to my attention. Apparently, some folks think that this accident may have been caused by Mast Rocking rather than an abrupt cyclic control input. I’m not convinced. Mast rocking supposedly does not cause the main rotor blades to diverge from their normal plane of rotation. How else could the tail be cut off in flight?

But what worries me more than putting stress on components is an accident report from 2006. I read this report on the NTSB Web site not long after the accident occurred. Back then, there was no known reason why an R44 helicopter with just two people on board for a long cross-country flight should fall out of the sky with its tail chopped off, but I had my suspicions. After my recent flight with the new pilot, I looked it up again. Here’s the probable cause (emphasis added):

The Canadian certificated commercial helicopter pilot was conducting a cross-country delivery flight with a non-rated passenger occupying the copilot seat. The passenger and pilot together had previously made delivery flights from the Robinson factory to Canada. Two witnesses saw the helicopter just before it impacted the ground and reported that the tail boom had separated from the fuselage. No witnesses were identified who saw the initial breakup sequence. Both main rotor blades were bent downward at significant angles, with one blade having penetrated the cabin on the right side with a downward slicing front to rear arc. The primary wreckage debris field was approximately 500 feet long on an easterly heading. The helicopter sustained damage consistent with a high-energy, fuselage level, vertical ground impact. Detailed post accident investigation of the engine, the airframe, and the control systems disclosed no evidence of any preimpact anomalies. The removable cyclic was installed on the left side copilot’s position, contrary to manufacturer’s recommendations when a non-rated passenger is seated in the left seat. The removable pedals and collective for the left side were not installed. The cyclic controls for both the pilot’s and copilot’s positions were broken from their respective mounting points. The copilot’s cyclic grip exhibited inward crushing. The Safety Board adopted a Special Investigation Report on April 2, 1996, following the investigation into R22 and R44 accidents involving loss of main rotor control and divergence of the main rotor disk, which included a finding that the cause of the loss of main rotor control in many of the accidents “most likely stems from a large, abrupt pilot control input to a helicopter that is highly responsive to cyclic control inputs.”

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
a loss of control and the divergence of the main rotor blade system from its normal rotational path for undetermined reasons.

(A full narrative is also available.)

This is pretty much what I’d imagined. The helicopter is cruising along at 110 knots in a very boring part of the California desert. For some reason, the pilot (or his passenger, who has access to a cyclic control), jerks the cyclic one way or the other. Maybe he was trying to dodge a bird. Maybe he was goofing off or pretending to be Airwolf. Who knows? The sudden input is enough to cause the blades to diverge from their normal path. One (or both) of them dip down and chop off the tail boom. The result: two dead bodies in a 500-foot long debris field.

And this is what was going on in the back of my mind when the pilot beside me made those sudden inputs.

Anyone who has flown a Robinson helicopter can tell you how responsive the cyclic control is. It wouldn’t take much effort to knock the blades out of their path. That’s why we’re taught — or should be taught — to use smooth control inputs.

Other accident reports like this one include: CHI05CA267 and MIA00FA102 (which is a “watch this” moment).

Other Concerns

Rotorcraft Flying HandbookThere are at least two other reasons to avoid abrupt cyclic movements. You can find all these in the Rotorcraft Flying Handbook, an FAA publication that’s a must-have in any helicopter pilot’s library.

Under the “Retreating Blade Stall” heading (page 11-6):

High weight, low rotor r.p.m., high density altitude, turbulence and/or steep, abrupt turns are all conducive to retreating blade stall at high forward airspeeds.

Personally, I don’t think retreating blade stall is an issue in Robinson helicopters, except, perhaps, at high density altitudes and high speeds. But in that case, you’d be exceeding Vne.

Under the “Low G Conditions and Mast Bumping” heading (page 11-10):

For cyclic control, small helicopters depend primarily on tilting the main rotor thrust vector to produce control moments about the aircraft center of gravity (CG), causing the helicopter to roll or pitch in thedesired direction. Pushing the cyclic control forward abruptly from either straight-and-level flight or after a climb can put the helicopter into a low G (weightless) flight condition. In forward flight, when a push-over is performed, the angle of attack and thrust of the rotor is reduced, causing a low G or weightless flight condition.

You can find an account of this (with a lucky pilot and passenger) in this accident report from July 22, 2010. Indeed, the problem may have occurred during the right turn the pilot initiated — did he jerk the cyclic over as my companion had done?

Another accident report that suggests mast bumping is SEA03FA148 (which took the life of a pilot I knew).

I’m Not Just Nitpicking

The point of all this is that I’m really not just nitpicking a fellow pilot with limited flight time. He performed a maneuver which I consider dangerous and I have all this information to back me up. It’s important for him — and for others who might not know any better — to avoid abrupt control inputs.

Robinson helicopters aren’t capable of safely performing aerobatic maneuvers. Don’t fly them as if they are.

Update, March 17, 2012: Here’s another example of an accident likely caused by an abrupt control input. This one resulted in mast bumping.