Not Crossing Dimensions
Not Crossing Dimensions
(OP)
I have a few rectangular shaped components in a Polar Array (corners touching) Thant I need to dimension. Unfortunately there are other components outside of the circle, so I'm going to have to dimension them inside, causing the dimensions to cross each other. Obviously this is bad form & I'd like to stop it happening.
Don't know if this is possible though, so does anyone have any suggestions?
Attached is a simplified version of my file, including some annotations to (hopefully) make what I'm trying to do clearer.
P.S. I hope it is obvious I don't want to have to explode the dimension in order to do this.
Don't know if this is possible though, so does anyone have any suggestions?
Attached is a simplified version of my file, including some annotations to (hopefully) make what I'm trying to do clearer.
P.S. I hope it is obvious I don't want to have to explode the dimension in order to do this.
RE: Not Crossing Dimensions
/edit/ More info about the nature of the part may result in more refined suggestions, such as whether or not it's practical to call out an inscribed arc radius to define orientation or not.
RE: Not Crossing Dimensions
Unfortunately I cannot give you any more information than I have. I don't think it would help anyway. If it is not possible then it's not possible, I'm sure I've seen it done though.
RE: Not Crossing Dimensions
You can "oblique" a dimension in the DIMEDIT command but it will shift BOTH extension lines by the same angle, in the same direction - it will not allow you to camber the extension lines inward or outward. It only ITALICIZES the extension lines, so to speak.
RE: Not Crossing Dimensions
RE: Not Crossing Dimensions
Nevermind, they can just deal with the Dims crossing each other.
Cheers anyway.
RE: Not Crossing Dimensions
RE: Not Crossing Dimensions
1)One way would be to use ordinate dimensions, but the dimension values may be a little weird.
2)If the dimensions are all similar, just dimension one feature and just use TYP as typical.
3) Use a table of to the side and dimension each feature with leaders that reference the table.
These are all simple solutions, please let me know if you use any of them.
Simplicity is OUR job.
Regards,
Ted
RE: Not Crossing Dimensions
RE: Not Crossing Dimensions
RE: Not Crossing Dimensions
Another option, you can always make the dimensions and then explode them, and shape them as you see fit. Obviously this renders the dimensions 'non-updating' and could be completely against your rules, and is generally bad form anyways.
A further option is the same as the second, but add the mid-line dimensions on a 'non-print' layer and make them into a reference parameter that you then reference in the text of the 'false' dimensions.
And then the other option, if you have only two or three different dimensions, dimension the first one [ 1200 TYP, Three (3) Places ] and put a single hash line across the border [ / ] of each similar, dimension the second [ 2400 TYP, Two (2) Places ] and put (2) simple hash lines [ // ] across the border of each similar, and so on. Basically indicating each unique feature in a coordinated fashion, notation also works (see note 1).