Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations SSS148 on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Scaling Imported IGES files.... 1

Status
Not open for further replies.

NickE

Materials
Jan 14, 2003
1,570
I am trying to import an IGES file into SW 2008. I can import it as either importedcurves or a 3d sketch. (its the centerline of a complex curve, similar to a helix)

The problem is that the imported curve is 25.4 times bigger than I need.

The sketch tool scale is not available....

how do I scale the curve to get it from reading in as inches, its actually metric.

(I can't change the way the iges file is made, its just given to me.)

nick
 
Replies continue below

Recommended for you

Have you tried importing it into a template with units set to millimeters?
 
Also check the "Units" option in the Open menu. Click he "Options" button after setting the file type to "IGES".
 
What application is the IGES coming from? There may also be a setting on their end also to help you. Or, they can send you a different file type SW can read.

Chris
SolidWorks/PDMWorks 08 3.1
AutoCAD 06/08
ctopher's home (updated Jul 13, 2008)
 
Example:

IGES file is in mm, object (curve really) is ~309mm end to end.

When imported using template setting under options menu, and the template is in mm, the evaluated Z height is measured at 7586.22mm.

When imported using the option to use file units the object ends up as ~309in end to end.

If I could just 3d scale the object by 1/25.4 I could get the size I need, just dont have any clue how to do this.

nick
 
You cannot use the scale feature in SolidWorks (not sketch, tool, but Scale Feature) after the geometry is imported? (If not, why not?)



Jeff Mowry
A people who value security over freedom will soon find they have neither.
 
Where is scale feature in the menus? I've only previously used 2003/2005 and now I'm on 2008.

nick
 
I think scale is not available for 3D sketches.
 
Bummer--I just tried it (v2007) and it's neither available for the 3D Sketch or a Composite Curve.

What an odd problem. Have you contacted your VAR about this--they ought to have encountered this problem before.



Jeff Mowry
A people who value security over freedom will soon find they have neither.
 
NickE,

Here's a possible workaround:

1) Generate a swept surface using the imported curve as your path. The profile should be such that the resulting surface creates edges that coincide with your imported curve.

2) Scale the swept surface appropriately.

3) Create a 3D sketch, extracting the edges of interest.

I believe this will yield what you're looking for, albeit with a few extra steps.
 
That should work great. A bit of a kludge to get what you need, but having a work-around of that type might get you rolling right away. Great idea, dgowans!



Jeff Mowry
A people who value security over freedom will soon find they have neither.
 
The curve I'm working with is a modified single helix, normally its swept with a circle of n diameter centered on the curve. (No edges!)I tried to sweep with a rectangle with one corner on the curve, doesnt work.

 
Try sweeping with a single line as your profile. Make sure one endpoint of the line pierces the path. You may need to make your profile line VERY short to avoid any geometry errors.
 
Didn't get a chance yet, will keep ya all posted.
nick
 
You cando a 3D sketch and use Convert Entity to extract the curves then do an extrude of the sketch in a direction. You should be able to scale that.

[jester]
 
============================================================
IGES file header per DRAFT v6 1998-01-05 18.
Global Section (reference 2.2 pg 18 Table 1)
============================================================

1) String Parameter delimiter character.

2) String Record delimiter character.

3) String Product identification from sending system

4) String File name

5) String Native System ID

6) String Preprocessor version

7) Integer Number of binary bits
for integer representation

8) Integer Maximum power of ten representable
in a single-precision floating point number
on the sending system

9) Integer Number of significant digits in a
single-precision floating point number on
the sending system

10) Integer Maximum power of ten representable
in a double-precision floating point
number on the sending system

11) Integer Number of significant digits in a
double-precision floating point number on
the sending system

12) String Product identification for the
receiving system

13) Real Model space scale

14) Integer Units flag (see pg 20; 1 = in, 2 = mm, etc.)

15) String Units Name ***** (Redundant unless [14] = 3) *****

16) Integer Maximum number of line weight
gradations. Refer to the Directory Entry
Parameter 12.

17) Real Width of maximum line weight in units.
Refer to the Directory Entry Parameter 12
(see Section 2.2.4.4.12) for use of this parameter.

18) String Date and time of exchange file generation
15HYYYYMMDD.HHNNSS or 13HYYMMDD.HHNNSS
where:
YYYY or YY is 4 or 2 digit year HH is hour (00-23)
MM is month (01-12) NN is minute (00-59)
DD is day (01-31) SS is second (00-59)

19) Real Minimum user-intended resolution or ******************
granularity of the model in units specified ***************
by Parameter 14. ******************************************

20) Real Approximate maximum coordinate value
occurring in the model in units specified
by Parameter 14.

21) String Name of author

22) String Author’s organization

23) Integer Flag value corresponding to the version
of the Specification to which this file complies.

24) Integer Flag value corresponding to the drafting
standard to which this file complies, if any.

25) String Date and time the model was created or
last modified, in same format as field 18.

26) String Descriptor indicating application protocol,
application subset, Mil-specification, or
user-defined protocol or subset, if any.

================================================================================
================================================================================

I'm assuming you have a standard Fixed Format ASCII file.

You can change the units using a text editor.
Use fixed width font, i.e. Courier.
This message should be viewed using same.

Global section fields are variable length (usually comma) delimited.

All lines are 80 characters.

Strings are prefixed with character counts, i.e. 63H, 22H in fields
[3] and [4] below.


The above was taken from (never to be implemented?) IGES 6.
The headers in IGES 5.x are the same.

Units are defined by field [14] or [15].

-----
Sample inch:
,,63HD:\MyData\Reference\Aircraft\Boeing\Boeing_3_Views\737-700w.dwg, G 1
22HD:\MyData\737-700w.igs,53HAutoCAD-16.0 (Microsoft Windows NT Version G 2
5.0 (x86)),87HAutodesk IGES Translator Mechanical Desktop.R7.0.43.0 (MarG 3
18 2003) from Autodesk, Inc.,32,38,6,99,15,63HD:\MyData\Reference\AircrG 4
aft\Boeing\Boeing_3_Views\737-700w.dwg,1.0D0,1,2HIN,211, G 5
8.30708661417323D-2,15H20040414.223429,2.90688854527066D-6, G 6
2906.88854527066D0,,,11,0,15H20020213.110902,; G 7
-----

Line 5 extracted:

aft\Boeing\Boeing_3_Views\737-700w.dwg,1.0D0,1,2HIN,211, G 5

indicates it's an IN(ch) file.
("1.0D0,1,2HIN,211," are fields [13] thru [16])

Line 5 modified so it will be interpreted as mm:
aft\Boeing\Boeing_3_Views\737-700w.dwg,1.0D0,2,2HMM,211, G 5

If your file has something like "4HINCH" in field [15],
change it to "2HMM" and <SPACE> the "G" back to #73.

HTH


-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.
 
That works Jeff4136, I replaced 1.0 with 0.03937HMM in field 15, now my Iges imports at exactly the right scaling.

Thanks


Nick
I love materials science!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor