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 :)


Comments

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

syslog-ng roadmap 2.1 & 2.2

We had a meeting on the syslog-ng roadmap today where we decided some important things, and I thought I'd use this channel to tell you about it. The Open Source Edition will see a 2.1 release incorporating all core changes currently in the Premium Edition and additionally the SQL destination driver. We are going to start development on the 2.2 PE features, but some of those will also be incorporated in the open source version: support for the latest work of IETF syslog protocols unique sequence numbering for messages support for parsing message contents Previously syslog-ng followed the odd/even version numbering to denote development/stable releases. I'm going to abandon this numbering now: the next syslog-ng OSE release is going to have a 2.1 version number and will basically come out with tested code changes only. The current feature set in PE were developed in a closed manner and I don't want to repeat this mistake. The features that were decided to be part of the Open

syslog-ng 3.0 and SNMP traps

Last time I've written about how syslog-ng is able to change message contents. I thought it'd be useful to give you a more practical example, instead of a generic description. It is quite common to convert SNMP traps to syslog messages. The easiest implementation is to run snmptrapd and have it create a log message based on the trap. There's a small issue though: snmptrapd uses the UNIX syslog() API, and as such it is not able to propagate the originating host of the SNMP trap to the hostname portion of the syslog message. This means that all traps are logged as messages coming from the host running snmptrapd, and the hostname information is part of the message payload. Of course it'd be much easier to process syslog messages, if this were not the case. A solution would be to patch snmptrapd to send complete syslog frames, but that would require changing snmptrapd source. The alternative is to use the new parse and rewrite features of syslog-ng 3.0. First, you need to f