Time dependant Gravity Input for shock Simulation in Creo Mechanism
- 1 reply
- 389 views
Please include detailed documentation such as screenshots, images or video.
1. What version of the software are you running?
CREO 7
2. What is the problem?
I was trying to perform shock simulation of 20g on a dynamic system which is basically an automotive plunger Relay. I gave 20g shock load as an acceleration profile for 45ms (attached find the snapshot of the same). When I gave this as an acceleration motor, creo converts the profile to displacement profile with available initial condition and give displacement profile as the motor. However, in reality i expect, the acceleration to be acting similar to how gravity works in creo mechanism. So as expected the analysis shows a failure due to the fact that displacement reaches beyond my constraints.
3. Are you using a workaround? If yes, please describe it.
Yes. The workaround I am doing is that, converting the acceleration to force by multiplying it by mass of moving parts. Thereby developing a force profile and giving this profile as external force to the system. By adopting this technique, atleast I'm seeing the results which I expected. Although I'm not sure whether the result is reliable or not.
My idea would be to provide a feature to the gravity load in creo mechanism where, I can add a time dependant acceleration profile to the system in addition to the constant gravity (g).
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
I am working in TE Connectivity GmbH which is having a close collaboration with PTC Creo. My department is working on Automotive Relay which have alot of moving components which is basically a complicated version of spring mass system. If this idea would be implemented it could help us alot in understanding the dynamic system in response to shock load even without building the actual sample and testing.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Our department is in total 65. Speaking of hours, we could save alot on the time needed to validate the dynamics of the system without even building the sample.
