Jump to content

CAD Model conversion


---
 Share

Recommended Posts

I have cad converter on Calypso. I have to use *.sldprt file and when load, it will convert to SAT. Everytime solidworks gets upgrade, I cannot load any model created from new solidworks version. I usually try contact a solidwork user to save file from *.sldprt file to *SAT. I know last time I was suppose get Calypso upgrade however at this time I can't get an approval for upgrade.

Since I do not have solidworks, is there a software that convert to SAT without getting Calypso upgrade?
Link to comment
Share on other sites

You can convert all supported formats directly in the AIDE, without any extra license. Its one of numerous exploits that one potentially could take advantage of.

Just saying.. 🙄
Link to comment
Share on other sites

I sent you a private message but, I don't think that option is working for some reason.
If you're not worried about proprietary sharing issues, If you want, I can convert the files for you until you find another solution, I use solidworks every day.
Send me a PM and I'll give you my email address or if that's not working, post you're e-mail address here and I'll contact you, if interested.
Link to comment
Share on other sites

Please sign in to view this quote.

I doubt any free CAD software will ever be able convert proprietary industrial CAD formats. The specs are not for free, so whichever software implements a converter will have to compensate the costs. Even demo versions of professional solutions usually deny access to stuff like this.
Link to comment
Share on other sites

Please sign in to view this quote.

I've never been able to get that to work. It just errors out on me. Most likely something I'm doing wrong though.
Link to comment
Share on other sites

Please sign in to view this quote.

Sounds like it.

Im like that kitten Norbert! I dont use it my self, since its somewhat cubersome and I have more CAD licenses then I need, some of them I dont even know what they are... 😕

I just like pointing out flaws to Germans. 🤣
Link to comment
Share on other sites

Please sign in to view this quote.

Me neither. I once played around with it a bit (found it myself), but came to the same conclusion as you. I almost never need anything else than our "native" CAD format NX. And if I do, I can use a central conversion tool to generate all the standard formats I need, or even better, instantly send it to e.g. a registered supplier, who receives it already conveted to the right format in one go.
Link to comment
Share on other sites

Glad to see that there are more lazy people 😃

But one could mock something like this up: https://youtu.be/2jQUYMeETO4
But in all seriousness, I will not contribute to anything legaly questionable. Just pointing the issues out..

I woulder if Zeiss would like to receive a list of all the "security issues" I have encouterd during the years, making the software a bit more secure. Maybe we can have a "hacker" competition, like Tesla?

I'll bet I can get Calypso to wash my clothes when I'm done. 😃
Link to comment
Share on other sites

Please sign in to view this quote.

🤣 🤣 Judging by my experiences in the past I seriously doubt that. 🙄
I've been using UMESS 300, UMESS-UX and now Calypso, and over all these years I often came to believe that Zeiss' CMM software programming department must consist of a group of left over 80s home computer programmers who missed out on the development of modern computers and their vulnerabilities.

My favorite security hole was part of the UMESS-UX installation:
Every now and then it could happen that a number of UMESS-UX files ended up with the wrong access rights set. Then UMESS would error out and the user had to call support. Zeiss had included a shell script to automatically set the correct rights on all UMESS files, so the support could quickly provide the user with a means to resolve the issue by themselves . But to be able to do this under a non-privileged account like ut16, they needed a way to set access rights with root privileges. Their "solution": They made a custom chmod command owned by root, gave it the SUID bit (!! 😱 ) and included it in the installation. This tool was then called by the shell script.
I guess the only reason why they weren't confronted with a massive amount of compromised UMESS installations was the fact that the average CMM user back then was far from being a computer ace.
Link to comment
Share on other sites

 Share

×
×
  • Create New...