Hi,
is there any way to export to STEP AP 242 in Rhino yet?
So far I was not able to find anything on that topic.
Thanks in adavance,
T.
4 Likes
Hi Tobias - no, there is not.
Can you tell us what this provides for you that is not in the 214 schema?
-Pascal
PLM/PDM data
1 Like
@pascal and @ivelin.peychev
Data like materials, etc… should be transported in the step-file.
So, yes, PDM/PLM-Data, including curves, etc…
So far, some software is not able to read curves transmitted in step-files (as far as my knowledge).
I’m going to breathe some life back into this subject.
I was informed by our sales team that we are receiving STEP files containing GD&T, but we are not seeing this in Rhino. The STEP files are AP242 schema. If we open the STEP file with e-dwgs we can see the missing information.
Is there a plan to include the STEP AP242 schema as one of our choices when importing (and exporting)?
Here is an example of what we are missing:
Thanks,
Dan
1 Like
Hi @chuck ,
Not sure if you noticed this one.
I can provide an example privately if you would like to take a look. Just let me know.
Thanks,
Dan
1 Like
Hi Dan. Sure, send your example. I don’t know when we would be able to add 242, but it does seem to come up lately.
Thanks,
Chuck
Hi all,
I just found an article showing specifications of Step AP203/214/242.
Look like Step AP203 and AP214 are withdrawn (ISO lifecycle stage 95.99) as International Standards. They were deprecated with the publication of AP242 in 2014.
I have used Rhino lot of times to get data from different file types and missing this one would be a pity, given that support for native Rhino files from CAE software is rare.
2 Likes
@theoutside, the link does not work for me.
try now, sorry public view didn’t get checked.
FWIW, you don’t need to view or even keep track of it. We’ll post here when/ if it’s fixed. The reports are for our internal devs, not necessarily the public, however in typically McNeel fashion we try to be as transparent as possible, thus the links.
@theoutside, yes. 
As AP203 and 214 are EoL, Rhino support for AP242 seems like a must. In any case, the extra features the latter supports would make it very attractive for a lot of people, especially those who have to data exchange between Rhino and one of the big-name solid modellers frequently. Porting things like dimensions and materials info both ways would be great.
3 Likes
Upvoting this…242 seems to bring over layer sets into Rhino from other apps as sell when I have the option to use 242 sending data to Rhino
2 Likes
Can we, the Great Unwashed, have some kind of statement from the Gods (aka McNeel) as to whether or not the intention is for Rhino to import and export AP 242 and if that’s a ‘Yes’, will it happen in R8?
Is there any movement on this? The AP242 is needed within manufacturing workflows. This would avoid a painful detour through Inventor. Thanks!
As it sits ATM, this is scheduled for v8 development.
3 Likes
Hi,
I’m having issues with delivering .Step files for machining. There seem to be incomplete/corrupted. It is fractionally harder to isolate the problem because I can only deliver AP203 and AP214 files and not AP242. The machining guys are saying that AP203 and AP214 are EOL and the issue might be in the software on their side not being maintained for these variants in their recently installed 2021 version of the software they use.
I’m not convinced that the problem is on their side as I am having similar problems with .IGES files but it would be nice to be able to tick the AP242 box and narrow in on whatever the underlying issue is.
I’m sure I’ll figure it out but I wanted to vote in favour of AP242 support sooner rather than later.
Hello - if the same problem also occurs in iges, then there may be something to fix in the geometry itself- can you send us a file or send to tech@mcneel.com with a link back to this topic in your comments?
-Pascal
A post was merged into an existing topic: Blocks make model extremely slow