Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.
I know that Motion requires a specific library of Visual C++ in order to run so I think your chances will be slim.
PTC already has retired Motion. Starting with Wildfire 3.0 you will not get MECHANICA Motion anymore, all customers with active maintenance on Motion have been provided with a upgrade possibility (1-2 years ago) to MDO. WF 2.0 is the last release with MECHANICA Motion still present, both in integrated and stand alone mode. Looking at the functionality and ease of use of MDO and knowing some of the pittfalls of Motion I would not bother with Motion too long. One of the major things lacking in MDO is 3D contact which will eventuallyappear in MDO also (WF 4.0 or 5.0). This was available in Motion but really tricky to use...
... and modeling contacts and compliant cams is exactly what I'm after! And flexible beams!
The issue that I have with MDO is that if I define a cam over a profile comprising several arcs representing a chain wheel outline, the cam will not follow the profile properly. In Motion you won't see such behavior, plus you can control cam smoothing. Even more, the contact model for cams in MDO is based on a coefficient of restitution rather that an impact (contact stiffness and damping). Again Motion seems to approach this in a better way.
Also defining custom loads seems cumbersome, since you have do use Pro/Toolkit.
These being said I can only tell that I really regret that Pro/Mechanica Motionis discontinued before MDO reaches a decent level of complexity, and my approach from now on is to look into some other dynamic simulation software, most likely ADAMS/View.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
