guitarguy1685 Posted October 31, 2017 Posted October 31, 2017 I'm trying to create a Dynamic Block for a Hilti KH-EZ concrete screw. I wanted to use a stretch parameter and chain an array parameter to create the threads as I change the lengths. The lengths for 1/4" screw start at 1-5/8" and goes to 4". I'm schematically showing the threads because I can't find any information about them. I just know the pitch is quite big. I started with a pitch for 1/4". But because the length starts at 1-5/8' when I get to 3, 3.5 or 4" the array doesn't complete. Is there a way around this? See my attached block below so you can see what I'm trying to describe. Hilti_Test.dwgFetching info... Quote
markwheeler303 Posted November 1, 2017 Posted November 1, 2017 Its purely because the array distance isn't a division of the total length required. the difference between the two is shown as that gap you are getting. I have played a little with it using constraints to try and get the end to stretch to fill the gap, but it requires a full redesign to accomplish. If exact accuracy is not required, I would set the length increments to match the array increments and set the lengths to be as close as possible to the desired lengths. I cant attach yet, but its an easy fix in the length properties palette. Quote
markwheeler303 Posted November 1, 2017 Posted November 1, 2017 Sorry you would need to add a table parameter for the set lengths for this to work. Quote
guitarguy1685 Posted November 2, 2017 Author Posted November 2, 2017 I figured it was something to do with non uniform increments. I also tried constraints earlier but couldn't get it to work. Quote
steven-g Posted November 2, 2017 Posted November 2, 2017 When using odd sizes like that you can't combine it with array, an array needs fixed values to work with, you need to rethink the design of how it works, either adjust the threads to match the array distance or use different parameters. Here's an alternative that uses a lookup, but then this method doesn't like working with a stretch parameter driving it. Hilti_Test (1).dwgFetching info... Quote
guitarguy1685 Posted November 7, 2017 Author Posted November 7, 2017 That's pretty clever. thanks for your help guys. Quote
iconeo Posted December 8, 2017 Posted December 8, 2017 Here you go with stretch. Hilti_Test.dwgFetching info... You need to use a double lookup along with another visibility state. Thanks. Quote
iconeo Posted December 8, 2017 Posted December 8, 2017 Here is what I use for THD. Not as graceful but it does the job. Hilti_Test2.dwgFetching info... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.