STEP File import question

[CNCAppsJames]

Anyone having trouble with Mastercam importing STEP models lately? My CAD is coming from Inventor Pro 2022 and I haven't had a single issue in almost 6 years with STEP... until Mastercam 2022.

There's 40 threaded fasteners, 20 parts (that have a lot of fine serrations), 20 pieces of stock, 40 Knife edge pitbull clamps, a pallet, and two tombstone-ish workholding fixtures.

STEP used to be my go to but recently SAT has been getting it done. Just wondering if I should send it in to QC or not. Don't want to waste their time if it's just me. I tried 203, which results in nothing to import and  214, and 242 crash Mastercam.

I'd share the file but I can't. It's DEFINITELY under ITAR restrictions.

Just wonderin'...

[gcode]

Maybe it's the output from Inventor Pro 2022?

[CNCAppsJames]

Definitely possible, but I've been using files from Inventor Pro 2022 since before Mastercam 2022 came out and had no issues prior.

I'll look into the data that came into Inventor (fasteners, workholding, clamps, etc...) also, and see if there's some commonality there.

[gcode]

It would be nice if you had Mastercam's Inventor translator
Then you could test the files in their native format.
Or Spaceclaim.. it can open Inventor files

[CNCAppsJames]

There was a reason at one time I stopped reading the native Inventor files in... but now I can't recall what it was.

The Inventor file read in fine. Sometimes the easy answer is the one overlooked.

Thanks G...

[gcode]

There was a reason at one time I stopped reading the native Inventor files in

Inventor was probably one release ahead of the translator
This is an inherent problem with using multiple software packages

I've been unsung MC2022 for most of this year, but MoldPlus just released its MC2022 CatV5 translator
I had the same issue with the Vericut Mastercam Interface for MC2022

[CNCAppsJames]

There was a reason at one time I stopped reading the native Inventor files in

Inventor was probably one release ahead of the translator
This is an inherent problem with using multiple software packages

Indeed it is. Hazards of the job.

New workflow;
1) CAD/Design
2)Read Native into CAM
3)If fail export and use STEP
4)If fail again, use SAT.
5)If fail again, go back to step 1 and find out WTF is wrong with the design and get it right in the CAD then repeat.

[PAnderson]

Don't forget that Mastercam native kernel is ACIS and that export format is X_T. I rarely have issues with STEP, even in Mastercam. Lately, I have been loading machine models with STEP and I have no issues. These files have over 1000 parts. In the past, I have had to load STEP into the AUTODESK data exchange utility and re-export into X_T format. I can usually tell what program they came from when they do fail, ProE or CATIA.

[gcode]

export format is X_T.

you can also use the X_B format
X_T is a text file .. you can open it and read it in a text editor ...
                             I wish I was smart enough to understand it

X_B is a binary file..  I've found they are a little smaller files and open quicker than
                                X_T.. but the difference is usually small enough that it is irrelevant

[CNCAppsJames]

Don't forget that Mastercam native kernel is ACIS Parasolid and that export format is X_T. I rarely have issues with STEP, even in Mastercam. Lately, I have been loading machine models with STEP and I have no issues. These files have over 1000 parts. In the past, I have had to load STEP into the AUTODESK data exchange utility and re-export into X_T format. I can usually tell what program they came from when they do fail, ProE or CATIA.

Free fiss.

[Jeff]

Anyone having trouble with Mastercam importing STEP models lately?

I import STEP files daily. No issues 99% of the time.
I don't know what software was used to model them though.

[Jeff]

Correction... the files I've been getting are STP, not STEP   if that makes a difference.

[JParis]

STP is Step...

There are different versions of it though, 203, 214, 219, 242

https://en.wikipedia.org/wiki/ISO_10303-21">https://en.wikipedia.org/wiki/ISO_10303-21

[byte]

export format is X_T.

you can also use the X_B format
X_T is a text file .. you can open it and read it in a text editor ...
                             I wish I was smart enough to understand it

X_B is a binary file..  I've found they are a little smaller files and open quicker than
                                X_T.. but the difference is usually small enough that it is irrelevant

Reading and writing to binary files is always faster than reading text.

[CNCAppsJames]

There was a reason at one time I stopped reading the native Inventor files in... but now I can't recall what it was.

The Inventor file read in fine. Sometimes the easy answer is the one overlooked.

Thanks G...

Threads?
Inventor does its "bitmap thready thing"....does that affect the native reading on import?

I don't think so. At least not in the recent files I've brought in. Actual threads on a part are about as useful as an elephant in a tree. It is a SERIOUS resource hog to model helixes for no real good reason than for eye candy.