Skip to main content
3-Newcomer
January 15, 2026
Solved

Mechanism analysis fails – cam pushing spring-loaded sliding pin

  • January 15, 2026
  • 2 replies
  • 197 views

Hello everyone,

I am having problems with a mechanism analysis in Creo.

I have a square sliding pin that moves along an axis using a prismatic joint.
The pin is preloaded by a spring.
An eccentric rotating disk (cam) pushes the pin upward, and the spring pushes it back when the cam rotates away.

The disk does not rotate around its geometric center (offset axis).

What I am trying to achieve

I need to evaluate the required driving torque of the rotating disk during the mechanism analysis.

What I have already tried

  • 3D surface-to-surface contact between cam and pin

  • Cam / curve follower definition instead of contact

Unfortunately, both approaches fail during the mechanism analysis with a “simulation failed / analysis failed” error.

Additional question (modeling):

I also need to place 48 identical sliding pins into corresponding grooves/slots around the disk.
Is there a way to automatically insert or pattern these pins without defining each pin manually in the mechanism?

Creo version: 12.4.0.0

KV_10664532_0-1768519934724.png

 

Any help or best practices would be greatly appreciated.

Best answer by skunks

Creo_test + MPG

2 replies

skunks19-TanzaniteAnswer
19-Tanzanite
January 30, 2026

Creo_test + MPG

3-Newcomer
March 10, 2026

Thanks for your solution, but what exactly was my mistake that caused it not to work for me?

19-Tanzanite
March 11, 2026

Unfortunately, I don't know.
My simulation license only works up to Creo 3, so I have to save higher versions as STEP and edit them with Creo 2 or 3.
I use special Creo templates for this.

Community Manager
March 9, 2026

Hi @KV_10664532,

 

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation. 

 

Thanks,
Anurag