metaruss

After almost 8 years of daily driving service, the Daytona was taken off the street for some badly needed attention.  The motor had been having oil system problems for a while: low pressure and was losing oil into the coolant and other places rather rapidly.  The body is also showing its age.

I’ve since swapped the motor for the original 2.2L Turbo I motor from my old 1988 Shadow.  It still runs as smooth as I remember.  I’m not sure how the Mitsu will behave with that giant, triple-core intercooler.  I had some interesting issues with boost oscillation in the Shadow when I was using a Conquest intercooler.  I am confident that a grainger can be used with a mixed pressure signal from the manifold (which causes oscillation) and turbo outlet (which causes creep) to keep the boost steady.  The cal is a stock 1987 CSX cal right now and the trans is a stock 1990 A523 with the OEM Turbo II clutch that held well in the Shadow.

I had upgraded my MythTV back and front ends recently from version 0.24 and ran into some annoyances:

• The MediaMonitor has a new dependency on the udisks daemon, even if you don’t use the Media Monitor feature.  Without it, Myth had very poor behavior when trying to eject optical media.  The eject option in the menu would just display a dialog saying “No devices to eject.”  Also, the physical eject button would get disabled after playing the disk even though I could eject it from a terminal with “eject” as the mythtv user.  The fallback in MediaMonitor::ejectOpticalDisk() seems to be useless.
• My carefully-crafted channel lineup for Comcast became non-functional.  This is such a tedious process that i still haven’t gotten around to fixing it.  Right now, my digital tuners are recording programs that can’t actually be tuned.

Thanks to the generosity of iMav at geekhack.org, I now have some real hosting for my sites.  So long, GoDaddy.

In other news, the new version of WordPress breaks an old plugin that I forgot I was using (PhotoJar).  I relied on its shortcode quite heavily, so many of my embedded photos no longer show up.  I will probably have to write some PHP glue to restore old posts.

The Phantom keyboard is a community-driven keyboard project. The goal was to build a tenkeyless mechanical keyboard with customizable firmware that would fit into a Filco or similar case. The keyboard controller is a Teensy 2.0 and the key switches are Cherry MX. This build uses lubed “ergo-clear” switches and is mounted in an acrylic case from Litster on GeekHack. The key caps are double-shots from a Cherry G80 with a few novelty keys from the Cherry Replica project.

Here is a comparison of the internals of the 3 big tenkeyless boards that are often discussed and recommended at GeekHack and other forums: the Filco Majestouch 2 (aka MJ2), the CM Storm Quick Fire Rapid (aka QFR), and the Leopold FC200. From the outside, the similarities of the MJ2 and QFR case design are obvious. They are both made by Costar and therefore use Costar stabilizers. However feature-wise the MJ2 has an attached cable and separate caps/scroll lock LEDs, while the QFR and Leo have removable cables attached from under the case and integrated LEDs. The Leo uses Cherry stabilizers. A nice touch on the MJ2 is rubber feet on the rear legs, which most other keyboards on the market lack.

The MJ2 and the QFR use the exact same method to support the plate. The plate is curved downwards at the top and bottom, which rests on the base. The plate thickness is the same (0.055″) and both are made from steel. The cases are the same material and about the same thickness (~0.110″). The only interesting difference is that the MJ2 uses 2 screws to hold the plate down on the base. Both clamp the plate to the base with the top half of the case, which snaps together in the same way and are locked together with one screw.

The Leo, on the other hand, has a plate that curves up and is supported by small ribs along the top and bottom. The plate thickness is the same, though, so this probably does not affect the feel of the board in any meaningful way. The case uses slightly thinner plastic, about 0.100″ – 0.105″ and snaps together with small tabs along the bottom edge (which make it much easier to open). It’s locked together with three screws.

The QFR and the Leo use a single-sided FR2 ~0.06″ PCB while the Filco uses a double-sided FR4 0.065″ PCB. The MJ2 and QFR both use a header-mounted controller (though not compatible) while the Leo has the controller built onto the main PCB. The slightly thicker and denser PCB material on the FJ2 is the only major thing that sets it apart from the other two.

Click on the pictures for detailed comparisons.

The Cherry MX switch lineup is somewhat lacking a “quiet” tactile switch that is really tactile. As a buckling spring enthusiast, I find the MX blue switches highly annoying both in terms of sound and feel. The click has a very high-pitched tick and ring to it and the tactile feel has an odd disconnect from the time the key is registered. This might be because the reset point is above the actuation point. MX brown switches are not really all that tactile to begin with, but at least they register the press at a more intuitive moment and they don’t have that annoying tick. Cherry also has a more tactile version of their brown switch, which has a translucent “clear” stem. The springs are quite stiff, which makes them tiring to type on for any length of time.

A very common Cherry MX switch modification in enthusiast circles is the so-called “ergo-clear” mod. This is where you combine the MX clear stem with the lighter spring from an MX blue/brown/red switch. I’ve decided, for me at least, that the ergo-clear provides the best typing experience that a Cherry MX switch can provide. It’s no buckling spring, but it comes close and is less noisy to boot.

Usually, most of the work is getting into the switches. If the switches are already in a keyboard, they have to be desoldered if they are the plate-mounted variety. PCB mounted switches can be popped open without desoldering as long as the switch does not have integrated LEDs. I’ve done this to a few boards now, but this time I am working with loose switches.

The switches are fairly easy to pry apart with a pair of small tweezers or similar tool. Some care is required during reassembly, but it is not that difficult. I also lube the stem guides with Silicone Teflon lubricant. This is a good idea with ergo-clears since the soft spring can have some difficulty overcoming the weight of the key and the friction of the tactile bump.

The soft spring is the longer one on the left.

This is the “Red Alert 2.0” key cap set that I got from a group buy on GeekHack. It is based on a similarly-named set that was run by KBTalking forums (Korea). While not quite as fancy, it still looks really sharp. It comes with red-on-white and white-on-red modifiers and Fn row.

This article was put into the GeekHack Wiki.

The KBC Poker X is a compact (60%) mechanical keyboard made by Vortex. Although it seems like it will be phased out and replaced by the Vortex Pure, it has a few advantages over it:

• The Poker uses completely standard key cap sizes so that any tenkeyless key set will work.
• The arrow keys are intuitively located both on the WASD cluster and on the lower-right modifiers.

It does have a few design problems, though. One is that the function lock on the Esc key (tilde) and on the lower-right nav keys is not reversible while holding Fn. Unfortunately, there is nothing that can be done about this. This is a particular problem when using vi or other cases where tilde is often used.

The other issue is a mechanical one. The PCB is mounted to the case at either end with screws, but there are no screws in the center. This causes the PCB to bow up slightly in the center, giving the keyboard a bouncy feel on the middle keys. Some folks have used a layer of thin foam between the PCB and the case to absorb this flex, but it doesn’t really address the root problem.

(continue reading…)

Here is the infamous Vortex “Race” 75% back lit keyboard. I’ve been using a KBC Poker X (a 60% keyboard) for a while with my laptop, so it is nice to have a real Fn row and a nav cluster of sorts. One has MX reds and the other MX browns. One or both will be “ergo-clear” modded at some point (MX clear stem with a blue/brown/red spring).

Here is the back lighting in action. It lets you set the brightness and lighting mode. One lame thing is that it forgets all the settings whenever it is reset. Another disadvantage is that it uses non-standard key cap sizes and profiles. So even if you give up the back lighting, you can only get other cap sets from Vortex. Vortex is a poorly-run company and I recommend avoiding working directly with them. Getting these turned into a bit of a mess over on GeekHack. The best thing is to buy them from a retailer that has them physically in stock.

This is the CM Storm Quick Fire Rapid with Cherry MX red switches sporting double-shot “Ragnarok Red” key caps from signature plastics. Much better than the gaudy caps it comes with. They have more texture to them, too.