Learning Forum

[martin.kopplow]

I just found that CAD translators in Discovery are READ ONLY.

I have been using Spaceclaim before, and translators were bi-directional there. This is a must have for us. Now, we 'upgraded' to Discovery but lost this very important feature. Is there a bi-directional translator package available for Discovery?

[Gaurav Sharma]

Hi Martin Kopplow

The Geometry Interface bundle enables bi-directional connectivity between CAD packages and Discovery AIM but for Spaceclaim, the connectivity is restricted to read only. Also, this holds good for both Discovery Spaceclaim and Legacy Spaceclaim. 

Can you please provide more details on what functionality you are trying to highlight here, because importing parameters or having a bidirectional connectivity is not a feature of legacy Spaceclaim either. 

[martin.kopplow]

Hi Gaurav,

maybe we have a misunderstanding here. We have 6 seats of 'legacy' Spaceclaim with added CAD-Dat Exchange Packages that enable reading AND writing of e.g. Catia files, als well as Parasolids, STEP, and about two dozen others. These do certainly exist, you may want to check your soures.

I installed Discovery a few days ago, also installed the translator package ( https://account.ansys.com/DiscoveryDownloadCAD ) and during installation it displayed the option "Read only" and "Bi-Directional" whereas bi-directional would not install without Workbench being present.

Now, after I got everything running and licensed, if I try to write a model to say a Catia 5 file, I do not get this choice of file formats any more. I attached the file type choice in the "save as ... " dialog for legacy Spaeclaim and Discovery as screen shots, to compare.

When I import or open, the choice in Discovery is identical to Spaclaim legacy, which leads me to believe it is now read only.

The lack of this choice in Discovery might well become a killer factor for Discovery in our company. Should this be discontinued for legacy Spaceclaim in the near future, we would certainly need to consider using something else, since we live in a multi-CAD-envirionment where a no hassle data exchange interface is crucial.

Though, maybe there is a solution other than that?

Best,

Martin

[Gaurav Sharma]

Martin Kopplow Thanks for elaborating and helping me understand better. Discovery SpaceClaim also includes Data Exchange I & II and thus, exporting the file to any desired format should not be a problem. Your observation is strange and unexpected, and might be due to some local issue that we will debug. I checked the same on my machine and am getting the expected exhaustive list under "save as" option, confirming that there is no such limitation with Discovery SpaceClaim: While I am discussing the matter at my end and will get back soon, can you please do the following check at your end: Go to File >SC Options > License tab and confirm if the option for Data Exchange I & II is active:   Regards, Gaurav

[martin.kopplow]

Hi Gaurav,

thanks for checking, so I knew it should in princible all be there and I'd need to look for issues on my end, which I did.

It appears that, by coincidence, the first model I tried to export after installing Discovery, had some wierd geometry issue. I have tried another one this morning, and with that one (and all following), everything worked as expected. Apparently, the full list is only being displayed, if valid or otherwise recognizeable geometry is present in the model. I was not aware of that. It can be reproduced by trying to export an empty model, the behaviour is the same, then.

My model was partly made up of imported geometry of unknown origin. After remodeling questionable areas, it now also exports with no issues.

I assume this case may be closed, then.

Regards,

Martin

[Gaurav Sharma]

Hello Martin,

Good to see you could figure out that the issue was with corrupt geometry.

Regards,

Gaurav