Skip to main content
L
LW_102525151-Visitor
1-Visitor
March 21, 2022
Question

STEP exports from CREO Parametric fail to import in other software products

  • March 21, 2022
  • 3 replies
  • 7778 views

Hi everyone. 

Not a Creo user myself, but trying to narrow down on a problem with one of our suppliers who use Creo. 

The provide (rather large, hundreds of MB to 1.x GB) complex models to us as STEP files which we fail to import.

 

We on our end use Autodesk tools (Inventor, Autocad, Navisworks) and another simple Step Viewer (not by Autodesk). That is, the models fail to import on at least two (if not three) different import kernels/backends. 

 

Of course I'm in contact with Autodesk support but cannot simply give them the models (yet)... IP rights/concerns, you know, lengthy progress to set up NDAs and such.

 

We did recieve working models form that supplier in the past ("Automotive" AP214 format) which were imported successfully. We then received a more recent model in AP242 format which we were not able to read (importers of all mentioned tools fail after endless hours of "thinking", as if the model causes infinite loops or such).

 

I've then asked to get a model again in AP214 format, but this does not import now, too.

At the same time we do recieve various step files from small to very large from other source applications / suppliers which we can import perfectly fine. 

 

Makes me think that either some particular part in that complex assembly is "bad", or ... idk.

 

So my question is: anyone got any idea on what the cause may be? Any "known problematic" options on the CREO export side settings that one should better leave out? Any hints would welcome, so that I can maybe test this through with the engineers on the supplier's side.

 

Does Creo Para create some sort of "export log" in which it would give warnings about problematic parts? The imports on my end unfortunately say "nothing" at all, just run, think, eat all available memory... and fail at some point (in touch with Autodesk on that, yes....)

 

Thanks,

Lars

3 replies

M
MartinHanak24-Ruby III
24-Ruby III
March 21, 2022

Hi,

please ask Creo user to export STEP and import it back to Creo. What does happen ?

 

It would also be good to know which version was used when AP214 STEP files could be imported and which is now in use.

L
LW_102525151-VisitorAuthor
1-Visitor
March 22, 2022

Hi Martin,

source says they always re-import their step exports before passing them on to us. So at their end, out of and then back into Creo, it works.

On our end, software hasn't changed.

Can I tell from the STEP header what version they use? There's the string " 'CREO PARAMETRIC BY PTC INC, 2020053' "

G**gle couldn't match that 2020053  (build number?) to any version list.

Thanks,

Lars

M
MartinHanak24-Ruby III
24-Ruby III
March 22, 2022

Hi,

the code is written in 1st line of any native Creo file.

 

Example:

1st line of native Creo part file ... #UGC:2 PART 1937 1460 815 1 1 15 3700 2020342 000002cc \

The code 2020342 belongs to Creo 6.0.5.1.

 

There is no conversion table ...

C
Chris321-Topaz I
21-Topaz I
March 21, 2022

Have you tried a parasolid?

 

If it helps attached is a 1 inch cube created in Creo 7.0.6 in AP214 and AP242 formats.

 

Also if you know any students or have kids that want to try Creo out, you could download the free student version and export out some more files to run trials on your end. The only limitation with the student version is that it doesn't intermix with the commercial version.

L
LW_102525151-VisitorAuthor
1-Visitor
March 21, 2022

Hi Martin and Chris,

Thanks for the responses and test files.

- Parasolid: no, not asked for that as a work-around (or rather: better option?) yet. Contractually, we always fix on STEP (as anyone is supposed to be able to handle that). Could be a next step to test that if we can't get it to work with STEP again.

- Test Cubes: those are imported without problems (just like many other steps from various sources).

- I've asked our partners to try the re-import into creo and also for some smaller sub-models to narrow down on the problem. 

 

Thanks for the hint on the test versions. Hope we get testing from the experts on the other side. They once managed to export similar complex assemblies which we could handle, so it should be a matter of getting the export profile back to what worked. Only I can't tell them what they did when it worked - that's not completely visible from the headers of the step files I believe. My first guess was AP214 vs AP242, but it turned out it wasn't that easy. Anyway, waiting on their response.

 

I'll be back once I have new information.

S
sacquarone21-Topaz I
21-Topaz I
March 21, 2022

Hello @LW_10252515 

 

What do you mean by "fail to import"? Do you mean:

  • Import succeeds but open gaps in surfaces (solidification not possible)? => If so playingwith different things in profile (use external accuracy, G2 fix on import for the surfaces, etc) may help

OR

  • Import fails with error? => If so, would be helpful to have the exact syntax of error faced upon import attempt to provide later further guidance

OR

  • Import attempt leads in an unexpected exit of Creo Parametric? => If so, you should have:
    • a Traceback.log file in working directory. Opening a case to PTC TS and attaching it will allow finding the signature of the trace, and hopefully share further guidance based on this anaylsis
    • a Trail file ending unexpectedly => Opening the trail file in a text editor sometimes help to identify at the very end which was the component which was attempted to be imported when exit occurred, and helps if you have this information, to maybe isolate it (from soft where STEP file starts from, beefore re-export WITHOUT this impacting object) before re-import attempt later in Creo Parametric

Regards,

 

Serge

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
March 22, 2022

Since the files seem to be coming from Creo 7, I wonder if there is something in the changes to handle multi-body that the STEP translators have not taken into account from the Autodesk side?

What version of Inventor are you importing these files into?

Have you imported other Creo 7 files into Inventor before?

Does Autodesk have an updated STEP translator?

 

L
LW_102525151-VisitorAuthor
1-Visitor
March 22, 2022

Hi Ben.

Inventor 2021.

 

And yes, we had Creo 7.0.0.0 STEP files (same build code, datecode 2020053 in the STEP headers) initially when the supplier's model wasn't that "mature"/detailed (but already similar in size, several 100MB). Those files imported fine, so the general combination of Creo 7 vs. IV 2021 works. 

And Creo 7 to Navisworks Manage 2020, and to Autocad 2020, and also to that other "Step viewer" we have (not Autodesk based) - all worked well with the same earlier large STEPs.

Something must be different with the more recent model the supplier exports for us. Probably something like mentioned by Ken above.

 

If no workaround-format (parasolid, iges) works we'll have to get NDAs and stuff in place and get the problem files to Autodesk in the end (will take time, needs NDAs to be signed etc etc...)

Will report on any progress we make one way or another.

 

Terms & ConditionsCookie settingsAccessibility statement