Note: This document was originally put together using the tools available in V2 Rhino. While these tools remain in Rhino V3 and V4, you may have developed different techniques for “repairing” troublesome IGES files. Please share those techniques here - John Brock

One powerful use of Rhino’s file translation ability is to clean up poorly written IGES files. You may have received IGES files from your clients or suppliers that do not read properly into your solid based modeling application. Often this is the result of an improperly formatted IGES file, missing or duplicate surfaces, gaps or overlaps, or bad surface trimming information.

No amount of relaxed tolerances in the healing process can automatically fix these problems. After a long wait, you end up with incomplete solids, missing surfaces, or perhaps nothing at all. Your job depends on importing and using this data. What do you do?

Rhino has the basic tools needed to overcome all of these problems. With a little practice and good problem solving skills, you can repair these problem files and get the data imported into your solid modeling application. The effort and time required will vary a great deal depending on the number of problems and the size of the IGES file.

Fortunately, most problem IGES files can be repaired fairly quickly with a little practice. However, some can take several days of effort. With Rhino you have the tools to fix the most difficult IGES problems and get on with the job.

Since Rhino is a surface modeler that supports solids, it does not require that the IGES data consist of a closed solid. Rhino will read in as much valid information from the model as it can, skipping corrupt objects but reading all the point, curve, and surface data. Rhino’s IGES importing process will often read the file and fix the problems automatically. All you have to do then is save it back as a new IGES file and read it into your application. If the repair isn’t automatic, you can use Rhino to replace missing surfaces, fix bad trim curves, smooth surface discontinuities, and export a solid model to your application.

Generally, you can salvage most of the data in the IGES file. Sometimes, there is no choice but to re-modeling portions of the file. Even in this extreme case, Rhino contains the tools to harvest isoparms, sections, and edge curves that can be used to replace these unusable surfaces while preserving the original design intent.

The general strategy in repairing IGES files will vary depending on the individual files. Over time, you will discover patterns of problems in the IGES files produced by specific applications and individual users.

1. Open</color> the IGES file. - <color red>Hide</color> or delete extra data - Use the <color red>SelDup command to find duplicate entities and move the extra ones to a “duplicate” layer and turn it off. You may need them later.
2. Use SelCrv and SelPt to select and Hide the curves and points - Use SelSrf to select all the surfaces and Invert the selection. This will leave any curves and points highlighted. Delete the curves that are not on or near the surfaces. Carefully inspect the remaining curves on the surfaces. These are probably the remains of incomplete trimming curves. Move them to another layer for later use. This will leave only surfaces on the screen.
3. Shade</color> and visually inspect the model - Does it look like you expected it to? Are there obviously missing surfaces? Do surfaces extend beyond where they should? The trimming curves needed to fix them may be saved on the layer from step 3. - <color red>Check</color> for bad surfaces - The <color red>Check and SelBadObjects commands will determine if some of the surfaces in the model have problems in their definitions. They may have stacked control points, bad edge curves, or a variety of other problems. Move these surfaces to a “bad surfaces” layer for later clean up.
4. Look at the units and absolute modeling tolerance settings in file properties - Are they reasonable? Most applications that can produce IGES files do not match the unit and tolerance settings without user intervention. Rhino does match the settings on export. Free-form surface modeling requires an intelligent compromise in modeling tolerance. NURBs curves are chains of polynomial expression segments joined by knots that carry continuity information between the segments. These segments are fitted to neighboring curves within the specified modeling tolerance. The tighter the tolerance, the more complex these curves become and system performance suffers. There is no point in calculating high density curve fitting to tolerance values that are not supported by your down-stream manufacturing processes.
5. Join</color> the surfaces - When joining, adjacent edges are tagged as joined if they fit within the specified modeling tolerance. If they are outside the tolerance, they are not joined. Joining does not alter the geometry. It only tags the edges as being close enough to be treated as coincidental. Look at the results on the command line. Did you get as many polysurfaces as you thought you would? Sometimes there are double surfaces after importing an IGES file. Usually, one will be complete and the second one will be missing interior trims. When the <color red>join happens, you have no control over which of the two surfaces it will select. If you suspect this has occurred, try joining two naked edges. If there is no nearby naked edge where one should be, undo the join, and select for duplicate surfaces. Delete the less complete surfaces and try the join again.
6. Check for naked edges - Naked edges are surface edges that aren't joined to other edges. During the join process, they were farther apart than the specified modeling tolerance. This may be from sloppy initial modeling, a misleading tolerance setting in the imported IGES file, or duplicate surfaces. If there are a lot of naked edges showing when you run the ShowNakedEdges</color> command, consider undoing the join and relaxing the absolute tolerance. It is likely that the original modeling was done at a more relaxed tolerance and the exported file setting wasn't true. Note: You can not improve the tolerance fitting between surfaces without substantial remodeling. - <color red>Join</color> naked edges or remodel - The joining of naked edges can be a mixed blessing. It is a trade off and may cause problems down-stream. If your reason for joining the edges is for later import as a solid or a meshing operation like making an STL file, using the <color red>JoinEdge</color> command will not generally cause any problems. If you will be cutting sections and most other “curve harvesting” operations, the sections will have gaps as they cross edges that were joined outside of tolerance. The gap to be spanned is displayed prior to joining. If the gap is less than twice of your tolerance setting, you can proceed without worry. If the gap is too wide, consider editing or rebuilding the surfaces to reduce the gap. <color red>Join</color> and <color red>JoinEdge</color> do not alter the surface geometry. They only tag edges as being coincident within the specified or override tolerance. - Repair the bad surfaces - It's best to repair one bad surface at a time, and join them into the main polysurface as you go. In order of least destructive method to most radical, the problems that caused them to fail check can be repaired by the following: - Rebuilding edges - Detaching trim curves and re-trimming - Rebuilding surfaces - Replacing surfaces - harvesting edges from surrounding surfaces, cutting sections through bad surfaces and building replacement surfaces from the collected curves. - <color red>Check</color> for bad objects - Sometimes joining surfaces that pass check can result in a polysurface that fails check. Generally this is caused by tiny segments in the edge or trimming curves that are shorter than the modeling tolerance. Extract the adjoining surfaces, check them, edit the boundary curves to eliminate these tiny segments, and join them back in. You are finished when you have a closed polysurface that passes check and has no naked edges. As you are joining and fixing surfaces, it is generally a good idea to run check from time to time as you work. - Export - Now that the IGES file has been cleaned up and repaired, you can export it as IGES, Parasolid, STEP, or ACIS for import into your application. There are differences between these formats. Some applications differ in their support of these formats. Experiment with all that are support by your application to determine the best format for you needs. =====Start with a Clean File===== The old adage, “An ounce of prevention is worth a pound of cure,” applies to IGES file transfers too. When possible, spending a little time in the originating application to export a “clean” file will save a great deal of clean-up work later. Unfortunately, this is not always an option. Two common creators of IGES data are CATIA and Pro/Engineer. The following procedures and settings will minimize the problems associated with importing IGES data from these applications. =====CATIA===== Export from CATIA by preparing the model mainly to improve the trimming curves. Here are the procedures one of our customers (Black & Decker/DeWalt) uses in CATIA to minimize their down-stream clean up tasks. {@ 1. To prepare the model for transfer, work with the volume: SOLID + EXTRACT + VOLUME 2. Clean the model and ignore all extraneous geometry: KEEP + SELECT + GEOMETRY + ELEMENT and select the “VOLUME” 3. Recalculate the boundary curves: Bring the old boundaries out of NO-SHOW: ERASE + NOSHOW YES:SWAP. Key in SPC - SUR and YES:SWAP to return. 4. ERASE and key in SPC - VOL 5. CURVE1 + BOUNDARY and key in *FAC 6. Run /CLN to check for errors 7. The model is now ready for IGES export. }@ =====Pro/Engineer===== To optimize export of Pro/E files into Rhino: Use these settings in the Pro/E “config.pro” file or save them as a “rhino.pro” file and read it in before exporting. {@ IGES_OUT_ALL_SRFS_AS 128 IGES_OUT_SPL_CRVS_AS_126 YES IGES_OUT_SPL_SRFS_AS_128 YES IGES_OUT_TRIM_XYZ YES IGES_OUT_MIL_D_28000 NO IGES_OUT_TRM_SRFS_AS_143 NO IGES_OUT_TRIM_CURVE_DEVIATION DEFAULT INTF_OUT_BLANKED_ENTITIES NO INTF3D_OUT_EXTEND_SURFACE YES INTF3D_OUT_FORCE_SURF_NORMALS YES IGES_IN_106_F2_AS_SPLINE NO IGES_IN_DWG_LINE_FONT YES IGES_IN_DWG_PNT_ENT YES IGES_IN_DWG_COLOR YES FIX_BOUNDARIES_ON_IMPORT YES }@ ProE File Exchange —- Information about successful exchange of Rhino files with Pro/E. Softimage File Exchange —- Information about successful exchange of Rhino files with Softimage. SolidWorks IGES File Exchange —- Information about successful exchange of Rhino files with SolidWorks.