Skip to main content

Extending a flap door's grip

I am not a pet-person, so we don't have any kind of pets. Kids sometimes are requesting this or that but so far our evasion tactics worked.

In any case, I was in one of these big "pet shops" the other day, because we have moved to a new house roughly a year ago and the old owners installed a flap door on one of the garage doors, like this:

 

As you might recognize the flap door was missing, and the plastic on the outside was pretty worn due to UV radiation. I've decided to replace it so I ended up buying this one:


Although I made an effort to pick the right one, however I failed miserably: I had to recognize that the 4cm width of my garage door is too wide for this kind of flap door:
  • the screws were not long enough (quickly remedied by buying a set of M4x80mm screws)
  • the two ends of the flap door didn't reach one another, there's a ~2cm gap between the two.

I ended up designing and then 3d printing the missing element. I used Blender for the design:

 

And then printed it via my CraftBot IDEX Flow printer (~6 hours):

 
 
 So the final product has become like this:


As you can see, there's a connecting "tunnel" between the two ends, which I hope would nicely cover the inner insulation of the garage door, both protecting it from the weather and giving us an aesthetic look.


I can't wait to install it :)


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

syslog-ng fun with performance

I like christmas for a number of reasons: in addition to the traditional "meet and have fun with your family", eat lots of delicious food and so on, I like it because this is the season of the year when I have some time to do whatever I feel like. This year I felt like doing some syslog-ng performance analysis. After reading Ulrich Deppert's series about stuff "What every programmer should know about memory" on LWN, I thought I'm more than prepared to improve syslog-ng performance. Before going any further, I'd recommend this reading to any programmer, it's a bit long but every second reading it is worth it. As you need to measure performance in order to improve it, I wrote a tool called "loggen". This program generates messages messages at a user-specifyable rate. Apart from the git repository you can get this tool from the latest syslog-ng snapshots. Loggen supports TCP, UDP and UNIX domain sockets, so really almost everything can be me...
17 comments
Read more

syslog-ng contributions redefined

syslog-ng has been around for about 12 years now, but I think the biggest change in the project's life is imminent: with the upcoming release of syslog-ng OSE 3.2, syslog-ng will become an independent entity. Until now, syslog-ng was primarily maintained & developed by BalaBit, copyrights needed to be reassigned in order to grant BalaBit special privileges. BalaBit used her privileges to create a dual-licensed fork of syslog-ng, named "syslog-ng Premium Edition". The value we offer over the Open Source Edition of syslog-ng are things that larger enterprises require: support on a large number of UNIX platforms (27 as of 3.1), smaller and larger feature differences (like the encrypted/digitally signed logfile feature) better test coverage and release management longer term support Although perfectly legal, this business model was not welcome in various Free Software communities, and has caused friction and harm, because BalaBit has enjoyed a privilege that no others cou...
Post a Comment
Read more

syslog-ng message parsing

Earlier this month, I announced the new syslog-ng 3.0 git tree, adding a lot of new features to syslog-ng Open Source Edition. I thought it'd be useful to describe the new features with some more details, so this time I'd write about message parsing. First of all, the message structure was a bit generalized in syslog-ng. Earlier it was encapsulating a syslog message and had little space to anything beyond that. That is, every log message that syslog-ng handled had date, host , program and message fields, but syslog-ng didn't care about message contents. This has changed, a LogMessage became a set of name-value pairs , with some "built-in" pairs that correspond to the parts of a syslog message. The aim with this change is: new name-value pairs can be associated with messages through the use of a parsing. It is now possible to parse non-syslog logs and use the columns the same way you could do it with syslog fields. Use them in the name of files, SQL tables or c...
1 comment
Read more