Set inclination angle, mass, friction coefficient, and initial velocity freely. Display all force vectors and position/velocity graphs in real time with automatic sliding/static friction determination.
Parameters
Incline Angle θ
°
Mass m
kg
Static friction coefficient μ_s
Kinetic friction coefficient μ_k
Initial velocity v₀ (downhill positive)
m/s
Negative = up the slope, Positive = down the slope
Velocity:
Results
—
Acceleration a [m/s²]
—
Normal force N [N]
—
Friction force f [N]
—
Time to Bottom [s]
Force Diagram & Animation — Drag the canvas to change θ
Visualization
Position s [m] vs Time t [s]
Velocity v [m/s] vs Time t [s]
CAE Applications
Friction contact analysis (Abaqus/LS-DYNA) parameter estimation / Friction condition verification for conveyor path design / Basic calculation for civil engineering slope stability analysis. Directly compatible with μ_s and μ_k used in LS-DYNA *CONTACT_AUTOMATIC.
What exactly is happening to an object when I place it on a sloped surface? Why does it sometimes slide and sometimes stay put?
🎓
Basically, gravity is trying to pull the object down the slope, but two forces resist it. The surface pushes up with a normal force, and friction between the object and the surface tries to hold it in place. In this simulator, you control the slope's steepness with the Incline Angle θ slider. Try setting it to a low angle like 10°—the object might not move. Now increase it to 45° and watch it accelerate down!
🙋
Wait, really? So friction is the key. But I see two friction coefficients, μ_s and μ_k. What's the difference?
🎓
Great observation! This is a crucial real-world detail. μ_s is the static friction coefficient—it determines the maximum grip before sliding starts. μ_k is the kinetic friction coefficient—it's the weaker friction acting during sliding. In practice, μ_s is always larger than μ_k. That's why it's harder to start pushing a heavy box than to keep it moving. Try setting μ_s to 0.5 and μ_k to 0.3 in the simulator. Give the object a small Initial velocity v₀. If the forces balance, it will stick; if not, it will slide with a lower friction force.
🙋
So the simulator decides "slip or stick" automatically? How does it calculate the acceleration once it's sliding?
🎓
Exactly! It checks if the component of gravity down the slope overcomes the maximum static friction. If it does, the object slides and kinetic friction takes over. The acceleration is then given by a neat formula: $a = g(\sin\theta - \mu_k\cos\theta)$. Notice that the Mass m cancels out! This means a heavy block and a light block slide down with the same acceleration if the friction is the same—a surprising result you can test instantly by changing the mass slider and seeing the acceleration value stay constant.
Physical Model & Key Equations
The core of the simulation is Newton's second law applied along the inclined plane. When the object is sliding, the net force down the slope is gravity's component minus the kinetic friction force.
$$ma = mg\sin\theta - f_k$$
Substituting the kinetic friction force $f_k = \mu_k N = \mu_k mg\cos\theta$ and simplifying (mass $m$ cancels) gives the governing equation for acceleration:
$$a = g(\sin\theta - \mu_k \cos\theta)$$
Where: $a$ = acceleration along the slope (downward positive) [m/s²] $g$ = gravitational acceleration (9.81 m/s²) $\theta$ = incline angle [° or rad] $\mu_k$ = coefficient of kinetic friction $\mu_s$ = coefficient of static friction (used for slip/stick condition check)
The condition for the object to begin sliding (to overcome static friction) is when the downhill gravitational force exceeds the maximum possible static friction force.
$$mg\sin\theta > f_{s,max} = \mu_s mg\cos\theta$$
Dividing by $mg\cos\theta$ gives the classic slip criterion:
$$\tan\theta > \mu_s$$
This inequality is checked in real-time by the simulator. If it's false, the object remains stationary ($a=0$). If true, the object accelerates according to the kinetic friction equation above. The normal force $N = mg\cos\theta$, which is crucial for calculating friction, is always perpendicular to the surface.
Frequently Asked Questions
It is determined by the coefficient of static friction μ and the inclination angle θ. If tanθ > μs (coefficient of static friction), the component of gravity along the slope exceeds the maximum static friction force, causing the object to automatically start sliding. The simulator automatically judges this condition and switches from a stationary state to sliding.
The position is the distance along the slope (positive direction downward along the slope), with units in meters. The velocity is also only the component along the slope, with units in m/s. Horizontal and vertical components are not displayed, so the design is intended to evaluate only motion parallel to the slope.
No, if the inclination angle is sufficiently large, the object will continue to slide. Depending on the relationship between the coefficient of kinetic friction μk and the inclination angle θ, if g(sinθ - μk cosθ) is positive, the object accelerates; if negative, it decelerates and stops. Additionally, if there is an initial velocity, the object may decelerate until the static friction force exceeds the maximum static friction force and then stop.
Gravity (vertically downward), normal force (perpendicular upward from the slope), friction force (along the slope and opposite to the direction of motion), and their resultant force (along the slope) are displayed in different colors. The length of the arrows is proportional to the magnitude of the force, allowing intuitive understanding of which force is dominant.
Real-World Applications
Conveyor Belt & Material Handling Design: Engineers use these exact calculations to design the incline of conveyor belts. They must ensure packages slide reliably without tumbling, which depends on the friction between the package material and the belt surface (μ_s and μ_k). Setting the angle too low causes jams; too high causes uncontrolled acceleration.
Vehicle Braking & Hill Start Assist: The slip/stick condition is fundamental for vehicle safety on hills. A car's brakes must provide enough static friction (μ_s) to prevent it from rolling down. Modern hill-start assist systems use sensors to detect incline angle and automatically hold the brake until the driver applies enough throttle to overcome static friction.
CAE Friction Contact Analysis (e.g., Abaqus, LS-DYNA): In crash simulations or metal forming analysis, defining accurate friction coefficients (μ_s, μ_k) between contacting parts is critical. This simulator's logic mirrors the core calculation in LS-DYNA's *CONTACT_AUTOMATIC card, where similar conditions determine when surfaces stick or slide relative to each other.
Civil Engineering Slope Stability: Analyzing soil or rock slopes for landslides involves a more complex version of this problem. The friction angle of the soil (similar to μ_s) and the slope angle are primary factors in determining if a slope is stable or will fail. This simulator provides the foundational physics for understanding these failure mechanisms.
Common Misconceptions and Points to Note
There are several key points you should be aware of to master this simulator, especially from a practical, real-world perspective. First, the coefficient of friction is not a constant determined solely by the materials. Textbooks might state that "the coefficient of friction between wood and wood is 0.4," but in reality, it fluctuates based on surface roughness, humidity, speed, and contact pressure. For example, the friction coefficient for a tire on dry concrete is about 0.7, but it can plummet below 0.4 when wet. When setting parameters in the simulator, it's crucial not just to look at a table but to consider "what are the environmental conditions?"
Next, the timing of the switch between static and kinetic friction. The simulator internally determines the "onset of sliding" and switches between them, but in the real world, this transition is continuous and doesn't happen instantaneously. In CAE software, how this is modeled in the "region of very low sliding velocity" significantly impacts analysis accuracy. Also, even if you set the initial velocity to "0," the object might start moving at a very slight angle due to computational rounding errors. This is an inherent limitation of numerical simulation, which you could also think of as mimicking the "extremely minute fluctuations" of reality. Achieving "perfect rest" is always difficult.