1 / 3
Garden Door Spacer for a Mortise Sashlock Mechanism. — image 1
1 / 3

Garden Door Spacer for a Mortise Sashlock Mechanism.

Order a print of this model

We calculate the final price from your selected file. You review and accept it before payment.

Saved on this device.

The door in the garden is mounted on a fence that its spacing moves from winter to summer, therefore we need a spacer.

Rating
0 / 5
Likes
0
Downloads
1
Makes
0
Views
30
Reviews
0

Updated at source:

Model information

License
Creative Commons — Attribution — Share Alike

1.- Introduction:

In the garden we have two entrance doors, mounted on a metal fence that slightly move during the year, therefore I need to have a spacer for the door latch that will allow the door to keep closed with enough tolerance for the fence position changes across whole year.  

Note: This model is only for the latch, it does not deal with the mortise lock if any.

Therefore I had the motivation to design a spacer, I can exchange during the year, one with 10mm width and one with 7mm width.

Explore my other Printables: https://www.printables.com/@rbid/models

2.- Printing:

No supports are needed, I suggest printing in PET-G but PLA will do the work as well although you are placing the spacer outdoors..

The only modification I did was to have the perimeters set to 3 instead of 2. (Prusa Slicer -> Print Settings -> Layers and Perimeters -> Vertical shells.

 

2.1 Regular Spacer (10mm):

File

Garden-Door-Sashlock-Spacer-10mm.3mf

Filament

6.47 mt. (19.08 gr.)

Time

51 min.

2.2.- Thinner Spacer (7mm):

File

Garden-Door-Sashlock-Spacer-7mm.3mf

Filament 

5.11 mt. (15.6 gr.)

Time

40 min.

 

3.- Change Log:

  • Upload: 2026-09-12: Initial Version. 
     

4.- Last Words

Please don't forget to ★ Rate and ❤ Like

Post your Makes to earn Prusameters!

Do not hesitate to ask questions, feedback is essential to making better models.

You are kindly invited to follow me to get updated when upload new models.

Happy printing & Greetings from the Galilee.

Hope it was not TL;DR