[79FT]: Building Things
... out of heavy machinery
|On:||Oct 12, 2018|
|In:||[Dream Shop] Tooling|
As we have established before, Fall for Russians is all about pickling things.
Last time it was an O-360. This time, it's tools for the new shop.
My current shop is all packed up and in storage, waiting for the actual shop to be built. Well, actually for the building to be gutted.
When I have built the new house, I have kept the old house. That's what's about to become my Dream Shop. Meanwhile, all my tools are nicely set up in my storage shed, waiting for their time.
I have sold most of my Chinese Grizzly crap I bought before knowing any better, and was hunting good, old, American-made machines for a while.
Okay, I settled for a Chinese-made Powermatic drill press, arguing with myself that it was in mint shape, dialed in with no obvious runout / shake, and would be my wood-only press anyway.
But two most important things wood-wise I still didn't have: a jointer and a table saw. Few had come up on Craigslist, and I would go over to check them out with all my dial gauges and a U-Haul trailer in tow.
I would spend close to an hour with each one of them, measuring all sorts of convoluted alignments and run-outs, only to find something very basic wrong with them.
One of these was a newer (mustard, but still American-made) PM60 jointer. It checked out reasonably well; until I asked the guy if I could adjust his fence square (I wanted to check it's warp by measuring squareness to tables along it's length).
"Sure Thing!" - he said, walked to a corner of his shop, picked up a hammer, and ... WHACK! - ... ... yeah. Call me a WHACK-o, but that is not how you adjust squareness... Not in my book. I felt for the poor machine.
I left, of course.
Another time I spent just south of 40 minutes with a PM66 table saw, only to check it's flatness dead last. Of course, it was so horribly bowed out of shape, I had to leave. And that was a 3 hour drive. Each way, mind you!
At any rate, yet another PM60 jointer popped up on Craigslist, and I grabbed a trailer in preparation of going to San Antonio the next day. That's where the jointer was.
Now, there was a rolling joke with one of the guys from the office - that he absolutely HAS to convince yet another guy from our office, his buddy, to sell me his PM66 saw - or, Russian Mafia will get him! Them both, in fact!
I kept it up for over a year; and I am not sure if that joke had made any contribution to this... but, he called me and said, "Roger is selling his Powermatic! Grab it, QUICK!". Same day as the jointer popped up.
Hah. So tomorrow I am about to go possibly pick up a jointer. Did I just land me a saw too?
I went to Roger's to dial the saw.
Arbor was shot, but trunnions were in great shape, and arbor for PM-66 is not a problem (someone still literally makes them and sells them on EBay). The tables were flat aside from a very tiny dip, a bit dirty at that, but alright.
I decided to pick it up.
So I did land me a saw and a possible jointer!!!
Next day (Friday), I rush to San Antonio to look at the jointer.
It was a green, older one, and it checked out good, except one minor mis-alignment of infeed and outfeed tables. I was trying to tighten them up a touch with gib set screws, and... I broke one of them.
The tables were flat, the motor was good, and the price was reasonable though, so I decided to buy it from the guy - especially after I broke it :).
Didn't take any pictures of jointer in transit... damn.
So, Friday night Im back, barely manage to roll the jointer off the trailer and into the garage, and Saturday I pack my wrenches and such to go break down the saw at Roger's.
See, it was set up with a large side table, router plate insert, and outfeeds - no way I would've been able to load all that; and besides, I don't need any of that aside from core saw. I already have all my router stuff from my previous shop (Incra no less).
It's raining. Damn.
I get to his place - he's gone for the weekend, his wife lets me in and leaves me alone with the saw and my tools.
About to begin.
Saw comes apart quite nicely.
Most of exterior stuff off, table's coming off next
I took off the fence, the side table, and the outfeed rollers. Side table goes into trash. Outfeeds and the fence I will sell (in fact, as of right now I sold the fence already - had three guys call me in the same day!). Yeah, I don't care for it. Incra's TS-LS any day over any other fence (and I have one :) ).
It was obvious no one has cleaned it inside. Likely, ever. Oh, well...
Remember, I said it was raining? I got a bunch of wrap, and plastic to cover the guts - I wouldn't drive under rain, but even the splash-back concerned me...
High-Tech Rain Proofing
Funny thing - when I was almost done, we got a nice break in the rain... So, I was able to load the saw up, and got it home without further adventures.
On the trailer
Later, in the next few days, I scraped together a vac and a compressor (remember, all my tools are packed away!), and cleaned it out. All important and not so important unpainted surfaces got a coat of either T9 or Corrosion-X, and she got wrapped back into plastic... The Saw, I will see you in a year or so...
And the jointer? Well, the jointer was clean already. So it just got wrapped too...
The only pic of the jointer I got
They're sitting nicely in the storage shed now, making acquaintance with my other toys.
And, there. Two most important tools? Done. Pickles out of metal done? Done. What's left?
A mandatory airplane pic, of course! Ken Wittekiend's PA-12 on floats on Lake Buchanan, first time ever I flew a seaplane! That was nice!
"Approach, how far from the airport are we in minutes?"
"N923, the faster you go, the quicker you'll get here."
...the long-needed updates
|On:||Sep 25, 2018|
|In:||[Misc] B Log|
|Tags:||tools, software, website|
After using the setup I did for myself in 2014 for a while, I decided it was time to change things around a bit.
... so yeah. I needed to add a static page, and I had a bunch of ideas about extra stuff I wanted to do for a while. But mostly, I just needed to add a damn static page, and thinking about coercing the existing setup into doing that with all the pictures I needed there was not making me happy...
... it was also about time I set this thing up so that I could actually log more projects than just a single airplane. Hey, I bet we all know - websites of this kind are mostly created to be later enjoyed by their authors in periods of 'I ain't got nothing better to do than review my old notes' mood ...
First of all, I wanted to be able to log multiple projects. The way the old setup was done was it had basically one project, under the section called "Build", and then this dangling catch-all "blog" thing for everything else.
But as you can see, most of articles here actually are NOT about the airplane I was working on at the time - the Skybolt - but rather, other little things here and there.
First thing I did, is I changed the way the files are laid out, and added semantics converting source content's directory structure to "Project / Section" semantics.
Each project now has it's own "sub-log" (that's what time logged is tracked based on). There is still a catch-all "blog" section, and a "default" project that can be configured if one so desires.
One more thing I realised is that the original version would only allow to log time if it was associated with an article-type entry... Flooding the Internet with tens of pages of "built three more ribs tonight" type stuff just to log time seemed kinda silly, so I added support for plain text log entries.
Articles still can track time; but you can also now have a separate text file with just "Date", "Summary", and "Time Logged" entries - one per line.
When creating the "log" page for a project, entries, being both from articles and from logfiles, are sorted by date, and then ones with articles associated with them will pick their summaries up from articles. Entries coming from text files will be displayed with summaries from log files.
All this time tracking functionality, structuring articles into projects, and such, were becoming an entity of its own large enough for me to justify clumping it all into a single Pelican's plugin, now called "b_log". I also added a bunch of config options to set up it's behavior.
Yeah. I killed it. This site Does Not Track You now. Because there's too much of this crap online.
Too many to count...
And finally, some silliness! I wrote another plugin that adds a "quote of the day" at the end of each article, randomly :) Enjoy; and I hope they will encourage you to read more articles (or at least, scroll thru them to get to the bits of wisdom).
I got happier now.
I have changed the B-Log notes to match the new setup, just so that there's one place I can send people to in case they are interested in my setup.
And I'm very close to posting that damn page, but...
...of course, I am restructuring the old content and modifying old pages instead to match what I got now, and writing stupid notes on what I did to the thing. Because, as we all know, making yourself a tool is as, if not more, pleasant, as using it...
A kill is a kill.
commonly used items
|On:||Aug 28, 2014|
|Tags:||tools, software, website, SWX|
Thanks to Bill Rose of the Biplane Forum fame, I have a lot of SolidWorks models of various hardware and other common airplane things.
I just recently have set up a page where you can grab all of them. Models are hosted on GitHub, so you will always get the most recent version.
The page is going to be linked in the Resources menu on the left. Click here to go straight to it.
"Sure you can have eight miles behind the heavy...there'll be a United tri-jet between you and him."
... and how it turns into two weeks
|On:||Jun 07, 2014|
So, originally it was supposed to be the shop day. I was gonna clean and put together the compressor I picked up off a gentleman on Craigslist, and set up the air hoses, filters and such - and then, back to CAD. And then..
See, I was looking for a bandsaw. I wasn't in a rush, so I was gonna pick up a good used one; so I was watching Craigslist and such, waiting and waiting. After doing that for about 6 months and after I got tired of not having one; I finally said "screw it" and bid on one on Ebay.
I won it on Friday around 4pm; paid, and went home. Well; there, in my Gmail's Inbox, was a notification from CraigWatcher saying that yet another bandsaw ad was posted... I opened it up; and couldn't believe my eyes.
Someone was selling.. an 18 inch Grizzly saw for 250 bucks! I couldn't pass on it; and next morning was driving back with a 300 pound beast in the back of my car....
... and then, spent a week and a half cleaning it up. I polished the rust out of the table; changed some bearings, re-cut threads on the blade tensioning rod, added a 4 inch dust port (for whatever weird reason, Grizzly decided not to put a dust port on this particular model).
It also ran on the 220, so I had to add a 220 outlet to the shop... Decided to go all out; and added a 6 gauge run with 50 amp breaker, so that I can run a TIG welder off of it when I get one.
So now; I own two bandsaws :).
Here's the perpetrator:
Since we're talking shop....
Right now Im set up in the garage of the old house we bought about half a year ago. Dash (my beautiful wife) is working on designing a new house we're gonna build; and that one is going to have a good sized shop. We will build that house first and then demo the old house; so I could start setting up earlier than I thought I would be able to; which is certainly nice.
But; Im dealing with 40 year old electrical; and other fun stuff..
Here are some pictures of that garage, ordered historically, as I was setting up.
Just after washing everything with a pressure washer...
The beginnings of the storage spot
.. all that empty space :)
That's pretty much all my tools before I moved (the big red chest is new)
First batch of stuff - table saw, jointer, planer, drill press. Excited!
.. and set up!
Storage's getting a bit more crowded
Setting up lighting. All that wood is for the benches.
First bench - the frame is ready.
The benches are up - and this place is starting to look like a shop!
Next, some 2x4s put together into a material rack. Cleared a lot of space!
Air setup, router table, and The Bandsaw
Added some entertainment :) Also, the little Delta bandsaw on the bench
I like how this looks!
And here are a couple pictures of the tools...
Air setup is very simple, a compressor with a shutoff directly into an air filter, regulator, and 25 feet of hose on a reel. That reaches pretty much everywhere.
The Air Setup (very simple for now)
At some point; I measured the runout on the drill press -- got around 10 thousandths - no wonder why it was all vibrating when drilling deep holes!
Grizzly includes very cheap chucks and arbors with their presses... Gladly, the bearings have no play though. I ended up picking up a used Jacobs chuck on Ebay, and boy, what a world of difference! Used a SouthBend arbor picked up on Amazon.
The Jacobs Chuck
I wanted a router table; but didn't want to pay around a grand for the one I like (and cheap ones are just.. crap, honestly); so I built one.
Top is two sheets of 3/4 MDF, laminated together. White Formica is laminated on top, bottom, and sides. All done with DAP Weldwood contact cement.
I bought the insert plate (though in hindsight, I should've just bought a hunk of aluminum and made it myself).
It still ended up being a bit out-of-flat, so I built a leveling system into the base (two bolts on each side are pulling the top "down", screwing into holes in the top with threaded inserts; and there are two screws pushing up on the top in the center of each long frame side. All that allows me to work out any non-flatness out of the top.
Fence is 3/4 ply; and the router sits in the box under the table. The box has 4 inch dust fitting epoxied on it on the other side (and the fence dust collector feeds into that fitting too).
The Homebuilt Router Table.
Everything is accomplished through teamwork until something goes wrong, then one pilot gets all the blame.
How I went about b-logging
|On:||May 20, 2014|
|In:||[Misc] B Log|
|Tags:||tools, software, website|
Note: this article was updated in 2018 to reflect changes I did in version 2 of B-Log. I want to have a single article to link to in case people are interested...
Notes on the update are here.
... was that I needed something to organize my builder's log. Being a software engineer by trade, I didn't want to go old school with paper logs and pictures, and whatever-random-collection-of-stuff-on-a-computer I could do. I wanted something that's easy to add entries to, calculates everything automatically, and allows me to publish it on the Web. Plus, I find it pleasant to view HTML as opposed to .doc, .pdf, or whatever.
Being a nerd, I just had to make it as nice for myself as I could...
Many-a-builder is using this apparently successful piece of work. Apparently, as of writing this, they have over 1100 logs published on their mykitlog.com.
I have played around with it quite a bit. The program is trivially simple; but I can't stand the way it's architected.
Oh, the Access databases. Basically, what this means to me as a user is if it ever .. erm.. decides to stop working, I will loose all my data. "Revert to a backup", you say.. Yes, but if the problem is that I can't add my N+1st record because the DB just corrupted itself, no backup will help -- I'm stuck.
On top of that if, god forbid, KitLog ever goes out of business, I am stuck with the data that I can't export w/o some serious reverse engineering.
No thank you. :)
So, I was toying around with other stuff.
Really cool (probably, second best to WordPress) blogging platform. Plus, links very nicely with Picasa, making image inserts a breeze.
The problem? How do I track time spent?
Also, the "going-out-of-business" problem was still there...
Now, that was better. Those are open source, good content entry and organization tools, and I can export it all out of a MySQL DB should I need to.
But, they require a server (which means either I'm running a server, or require hosting). And frankly, I believed that there must be a better way...
Close, but no cigar. Sphinx is the documentation framework used by Python and many others (including the company I work for).
It takes a bunch of ReST files as input (more on that later), and runs them through a converter, producing whatever you want (there are writers for html, txt, doc, pdf, and so on). The parser and converter is called docutils.
The problem with Sphinx is that it's geared towards writing documentation, and frankly, felt a bit too heavy to me for writing a builder's log.
While googling about yet-another-thingie-I-wanted-to-figure-out-about-Sphinx, I stumbled upon an article that talked about static site generators. There lied the Holy Grail....
The Pelican. I fell in love with this thing almost immediately. Here's what it does:
I did the initial version in 2014 (the date of this article). Then, I've spent about a week tearing it to pieces and figuring out how it works, and adding a few plugins to add things that I needed for the B-Log that it didn't have. I added time tracking, changed layout, got a Bootstrap-based template and modified it, etc.
In 2018, I fixed some suff and added a few more things.
You be the judge of results :).
Here's what I've done, in the end:
I like the end-result. I enjoyed hacking at it, and this was the first time I touched Python (so had to learn that on the way). Pretty neat (though I still prefer Perl (now, why do you need lists and tuples and sets again? :) ).
The only drawback is that it's regenerating everything every time. You can easily see how that might become a problem when you get a lot of entries, but I'm feeling like I'm ways away. 30 pages take about a second. I think I will need a lot of records before this becomes a problem; and at that point I will rewrite the whole damn thing to cache stuff.. probably :)
The code is here. The repo includes my theme, plugins, some tools, and sample content. It requires Python (I used 3.6 and did not test anything else), Pelican (which is checked into the repo in pelican/, along with it's dependencies), and Pillow (pip install pillow). Oh yeah, and pelicanconf.py's PATH_METADATA will likely require tweaking of slashes on Windows.
Read the config file (pelicanconf.py); and read thru Pelican docs to get the idea. sample-content/ contains my sample generated content that I was testing with. content-gen/ contains the simple Perl script that generates as much sample content as you want.
To me as an end-user, it looks like this.
My source files are organized in directories like so:
/project-one/section-one/ 2001-01-01-entry-one/ entry-one.rst picture.jpg section-one-log.log /project-one/section-two/ 2001-01-02-entry-two/ entry-two.rst picture.jpg section-two-log.log /project-two/section-one/ 2002-01-01-entry-one/ entry-one.rst picture.jpg /project-two/section-two/ 2002-01-02-entry-two/ entry-two.rst picture.jpg
and so on. Note the text *.log files - those are just log entries without the articles. They are optional, as you can see in Project Two.
Text log files look like this:
2011-01-01 | Some Summary Here | 1.02 2011-01-02 | Some Other Summary Here | 2.02
Note the separator - that's configurable :).
There can be as many log files in a "Project/Section" as one wishes, they will all be parsed, and all entries will be properly sorted by date.
There can be entire sections without articles - but a project must have at least one article to be properly displayed. Yeah, you got to at least declare your intentions :).
This directory structure will get parsed into two Projects (Project One and Project Two) with their separate logs. Each project will get it's own menu on the left. To display the menus, B_LOG_PROJECTS_MENU config var should list them.
If there was any time logged in a project (either in article entries, log files, or both), that project's menu will get an extra "Log" entry, which will neatly display all log entries, and some totals.
There are a few special directories I use, pages (configurable in PAGE_PATHS) for static pages (ie, About section of this site is a static page), and blog, for blog entries (they don't show up under any projects).
If I want a new article-type entry, I just add a directory in the project/section path, and start writing the article in my favorite text editor (VIM!!). If I decide to log time, I just use my special logged metadata entry at the top of the article. I drop images into article's directory, and use my figure ReST directive to reference them.
If I just need to log some time without polluting the Internet too much with useless text, I add it to an appropriate .log file, or create a new one.
If I don't want to log time, I don't have to - I can just post an entry into the project w/o time logged.
After I'm done, I run Pelican, which generates the full website (html, images, everything!) into an output directory. Voila! I can stop right there, and I will have a fully working local version of my log, since it's all static HTML, but we want this online, don't we? So, the only thing left is...
This was another revelation. Apparently, GitHub hosts static pages! 'Uploading a site' is a git push, and it transfers only deltas, so no fiddling with FTP, rsync, or whatever! They allow custom domain names instead of username.github.io, all you need is to set your A records in your DNS to point to their servers. It's awesome!
I am very happy with this so far. I have all my logs in practically plain text format, parser for which is open source and available. I have it nicely organized, and I can back it up as I please (to GitHub, anyone? :) ). I can re-write the programs that parse and produce final .html. I can extend the generator and change the theme to produce a printable version of the log, styled for paper rather than web. The list goes on!
A helicopter is a collection of rotating parts going round and round and reciprocating parts going up and down - all of them trying to become random in motion.
© Copyright "79FT". All rights reserved. Feel free to cite, but link back to the pages cited.
This website only shows how I did things in my various projects. These pages are for information and personal entertainment only and not to be construed as the only way, or even the perceived correct way of doing things. You are responsible for your own safety and techniques.