Errors while opening Inventor 2009 files

[Rolling Paper]

PLEASE HELP! I cannot open parts!!

When attempting to open an Inventor 2009 part (.ipt) in MCX3, I get the following error within MC:

"An unknown error has occurred. Please restart Art to return to last known stable setup. Then we recommend to save your work for back-up purposes."

 

After clicking "Okay" I get this:

 

"Error: save file is from a later version of Acis"

 

I click "Okay" again and the part does not open at all.

I am running MCX3 on a 64 bit system with XP x64. It is a fresh install of Windows and I've re-installed MCX3 twice now only to get the same error.

[Guest]

Did you install the x64 bit version of the Inventor View?

 

There are 2 versions

[Rolling Paper]

Yeah, I have a seat of Inventor 2009 and it is the 64 bit version (It comes with Inventor View 2009). I downloaded the Inventor View 2009 (64 bit version too) file from the MCAM website; when I tried to install it it wouldn't install because the version of Inventor View I already have installed is a newer version.

[malibu]

Rolling,

wait for new update ,it is not working for me either.

I am using x2 for inventor files.

[Tony35]

anybody from cnc got any ideas on a work around?

[Christian Raebild]

Since you have a seat of Inventor, try saving the file in Inventor 2008 format and see if Mastercam will open it then.

 

Alternately, you might try saving it as an ACIS .sat file (make certain it is ACIS R19 format or earlier).

 

While that adds a step to the conversion process, it might get the file imported.

[Rolling Paper]

Same results for a 2008 version file. (For some reason Inventor does not actually allow you to save a file as an earlier version anyway. )

I am able to save the file as a parasolid (.x_ and MCX3 opens it with no problems. So at least I have a work-around for now.

[Pete Rimkus from CNC Software Inc.]

This is problem (involving opening SAT, Inventor, or AutoCAD files which contain solids - anything ACIS-based) that does pop up occasionally in X3 and earlier releases (though perhaps with a different error messag) and has been corrected for the upcoming maintenance update.

Sorry about that.