Floating-pinion contact-loss check
ID: floating-pinion-contact-loss-check
A floating-pinion contact-loss check tests whether the motion predicted by a floating-pinion balancing mode remains compatible with every contact assumed to be compressed. It prevents a two-contact linear solution from being extrapolated into tensile tooth forces.
For the symmetric modelwith , mismatch , displacement and fixed mean approach , both contacts are compressed only whenAt equality one modeled force is zero. Outside the interval the linear expression makes one force negative; the unilateral model must replace that value by zero and the force-balance equations must be solved again.
Write and define the floating-pinion compression marginIf the motion satisfies , then is sufficient to retain both contacts. For a steady single sinusoid of amplitude and fixed , the maximum of over a complete cycle is , making the condition exact for that stipulated motion.
An original example uses , and . The margin is . A sinusoidal amplitude retains a minimum compression ; with , the smallest contact force is . Amplitude instead makes the unconstrained formula reach , revealing a contact-loss inconsistency rather than a physical tensile contact.
For a damped transient, an amplitude envelope is a sufficient bound but need not be attained at the phase where contact is least compressed. Failure of that sufficient envelope test therefore calls for examining the actual trajectory; it is not automatically proof that a real contact opened.
A controlled dynamic test can compare displacement with load-sensitive observations and check whether the assumed contact set persists. The historical face-gear program examined mounting freedom and torque division under slow rolling; it did not validate every possible dynamic contact assumption.[ref]
Development of Face Gear Technology for Industrial and Aerospace Power Transmission by Gregory F. Heath and others. Introduction, printed pp. 1–2; Conclusions, printed p. 84, floating versus constrained mounting
New to topics? Read the docs here!