Hole Dimension 'THRU ALL'
Jay Greenfield
callouts so I can edit it to just say 'THRU'. One .dll came up in a search
but I'm hoping that the solution to this problem isn't replacing it manually
every time I use a hole callout...anyone else get around this yet?
Jay Greenfield
Machine Designer
Carlsbad, California
Dale Dunn
news:g2Jka.3181$mH.9...@news3.news.adelphia.net:
Search for calloutformat.txt and calloutformat_2.txt in the install
directory. Search the help for that too to get some important information.
--
Dale Dunn
Design Engineer
www.jamestool.com
Jay Greenfield
too but it didn't look like you could edit the actual value for hw-holedepth
(or whatever it's called). I'll look more closely tomorrow...
Jay
"Dale Dunn" <daledun...@jamestool.com> wrote in message
news:Xns9357D2ED5AC67da...@65.24.2.12...
Jim Sculley
> I looked at that file and the sister, less grownup file (calloutformat.txt)
> too but it didn't look like you could edit the actual value for hw-holedepth
> (or whatever it's called). I'll look more closely tomorrow...
It's not there. Perhaps it is in the mdb files.
Jim S.
Chris Angevine
I've been trying to change the THRU ALL as well, with no success. If
you happen to get an answer, please let me know. I tried changing the
calloutformat.txt file. I replaced the <hw-thru> with THRU. No luck.
Dale Dunn
> I looked at that file and the sister, less grownup file
> (calloutformat.txt) too but it didn't look like you could edit the
> actual value for hw-holedepth (or whatever it's called). I'll look
> more closely tomorrow...
Ah. Those I don't know how to edit.
cupaday
Dale Dunn wrote:
> "Jay Greenfield" <jgr...@adelphia.net> wrote in
> news:6lMka.3193$mH.9...@news3.news.adelphia.net:
>
>
>>I looked at that file and the sister, less grownup file
>>(calloutformat.txt) too but it didn't look like you could edit the
>>actual value for hw-holedepth (or whatever it's called). I'll look
>>more closely tomorrow...
>
>
> Ah. Those I don't know how to edit.
>
And run replace 'THRU ALL' with 'THRU'
Chris Angevine
that needs to be modified is calloutformat.txt. The file is broken up
into sections; COUNTERBORED HOLES, PLAIN HOLES, etc. Below is a sample
for the plain hole callout. The "<hw-thru>" variable is what puts in
the "THRU ALL" comment.
** PLAIN HOLES **
HOLE-THRU=;<MOD-DIAM> <hw-diam> <hw-thru>
*with farside csink*
Just replace that variable with the word 'THRU' as shown below.
** PLAIN HOLES **
HOLE-THRU=;<MOD-DIAM> <hw-diam> THRU
*with farside csink*
This will work for almost all the hole callouts throughout the file.
The only screwy one is for the tapped thru callout. Below is a sample
from that section.
** TAPPED HOLES **
*with cosmetic thread*
TAP-DRILLTHRU(ct)=<MOD-DIAM> <hw-tapdrldia> <hw-thru>;\
<hw-threaddesc> - 2B <HOLE-DEPTH> <hw-threaddepth>
Here you change the tap drill callout to THRU just like the previous
example. But the thread description will still come thru with 'THRU
ALL'. The way around that is to change the '<HOLE-DEPTH>
<hw-threaddepth>' to 'THRU' as shown below.
** TAPPED HOLES **
*with cosmetic thread*
TAP-DRILLTHRU(ct)=<MOD-DIAM> <hw-tapdrldia> THRU;\
<hw-threaddesc> - 2B THRU
Using Find and Replace throughout this file makes it go quick. Make a
backup of this file first.
Good Luck
Jay Greenfield
then it didn't have to be a variable anymore! Doh! I can't wait to get to
work and ix this thing!
Jay
"Chris Angevine" <cang...@calvauto.com> wrote in message
news:cd8d6d12.03041...@posting.google.com...
Andrew Rodgers
<nic...@wisdomteeth.tlanta.com> writes
>
>It's not there. Perhaps it is in the mdb files.
>
>Jim S.
>
it.
SW2001+ SP0
Is this a new feature?
--
Andy Rodgers
Dave H
in drawings.
Dave H
"Andrew Rodgers" <an...@lintech.demon.co.uk> wrote in message
news:QVWBzSZH...@lintech.demon.co.uk...
Doug Dorton
It took me a minute to understand your complaint.
I'm using SW2003 and I've never had my hole call-outs indicate 'THRU
ALL.' They always come out as 'THRU.'
It seems that when you use Hole Wizard, if you select the 'End
Condition & Depth' as 'Through All,' then you get 'THRU ALL' as your
call-out. If you select 'Up To Next' as the 'End Condition & Depth'
you get 'THRU' as your call-out. I alway select 'Up To Next' and alway
get 'THRU.'
Could this be a simple solution to the 'THRU ALL' vs. 'THRU' problem?
Hope this helps,
Doug
"Jay Greenfield" <jgr...@adelphia.net> wrote in message news:<ozola.145$1K5....@news3.news.adelphia.net>...
Jerry Steiger
news:126af581.03041...@posting.google.com...
> If you select 'Up To Next' as the 'End Condition &
Depth'
> you get 'THRU' as your call-out. I alway select 'Up To Next' and alway
> get 'THRU.'
Doug,
I recall reading in this group quite some time ago that "Up to Next" is much
slower than "Through All" or "Blind" or "Up to Surface", since the software
has to search the whole part to find the next surface. Seems like you could
take a pretty significant hit if you have a lot of through holes with
callouts.
It would be nice if SW would just fix the silly callout.
Jerry Steiger
At Work Computers
Jay Greenfield
and that has fixed everything. It WOULD be nice if it was worded properly to
begin with, though maybe THROUGH ALL will become a new standard...
Jay
"Doug Dorton" <dbdo...@hotmail.com> wrote in message
news:126af581.03041...@posting.google.com...