1.3.13 · D5 · HinglishWork, Energy & Power

Question bankSpring-mass systems — collision problems

2,332 words11 min read↑ Read in English

1.3.13 · D5 · Physics › Work, Energy & Power › Spring-mass systems — collision problems

Shuru karne se pehle, har symbol ko dobara anchor karte hain jo hum use karte hain, taaki kuch bhi abrupt na lage. Yeh us poore page ka setup hai — frictionless ice par do blocks ke beech ek spring:

Figure — Spring-mass systems — collision problems
Figure — Spring-mass systems — collision problems

True or false — justify

TF1. Spring collision ke instant of contact mein kinetic energy conserved hoti hai.
Yeh ek general claim ke roop mein False hai — spring force hi contact force hai, aur bilkul pehle instant mein spring muskil se squish hoti hai, toh woh force (jab ) aur uska impulse tiny hota hai; almost koi momentum ya energy exchange nahi hua. Tum encounter ko momentum se track karte ho, aur KE sirf poore encounter mein hi conserved hoti hai kyunki ideal spring baad mein sab kuch return karti hai jo usne store kiya tha.
TF2. Spring maximum compressed hoti hai theek jab incoming block momentarily rest mein ho.
False — yeh maximum tab hota hai jab dono blocks same velocity () share kar rahe hon, yani relative velocity zero ho. Incoming block tab usually abhi bhi move kar raha hota hai.
TF3. Ideal spring se joined do free blocks ke liye, overall outcome ek perfectly elastic collision hai.
True — ek ideal spring KE store karti hai phir uska 100% return karti hai, toh before-and-after KE match karti hai, jo elastic ki definition hai (dekho Elastic and Inelastic Collisions).
TF4. Momentum conserved hoti hai jab ek block wall se bolted spring se takraata hai.
False — wall ek external horizontal force supply karta hai, isliye momentum conserved nahi hoti; sirf mechanical energy hoti hai.
TF5. Maximum compression par system ki kinetic energy zero hoti hai.
False — poora system abhi bhi par drift karta hai, isliye drift KE bani rehti hai. Sirf relative-motion KE, , spring mein stored hoti hai.
TF6. Agar ek clip spring ko maximum compression par latch kar le, toh encounter perfectly inelastic ban jaata hai.
True — blocks par saath lock ho jaate hain, aur stored hamesha ke liye trap ho jaati hai, jo exactly inelastic ki pehchaan hai.
TF7. aur ke roles reverse karne se maximum compression change hoti hai.
False — relative speed aur symmetric par depend karta hai ( swap karne se unchanged rehta hai), isliye depth same hoti hai.
TF8. Agar dono blocks same velocity se start karein, toh spring phir bhi thoda compress hogi phir push back karegi.
False — shuru se zero relative velocity ke saath, gap kabhi nahi shrinkta, isliye . Kuch bhi compress nahi hota.

Spot the error

SE1. "Spring ideal hai, isliye energy hamesha conserved hai — toh collision mein main use karunga."
Error timing ka hai: tum initial KE ko spring PE se first contact par equate nahi kar sakte, jahan hota hai aur almost kuch exchange nahi hua. Energy sirf tab clean hoti hai jab tum poori compression mein stored PE ko sahi track karo aur drift KE subtract karo.
SE2. "Do free blocks: saari KE spring mein jaati hai, isliye ."
Galat — system abhi bhi par move karta hai, drift KE carry karta hai jo store nahi ho sakti. Sirf CM-frame part spring PE banta hai; tumhe subtract karna hoga.
SE3. "Max compression tab hoti hai jab target block apni top speed reach kare."
Target ki speed max compression ke baad peak karti hai, jab spring usse forward push kar rahi hoti hai. Compression equal velocities par peak karti hai, spring re-expand hone se pehle.
SE4. "Block wall-spring se zyada speed ke saath bounce karta hai jitni se aaya tha, kyunki spring usse push karti hai."
Nahi — ek ideal spring exactly utni hi energy return karti hai jitni usne store ki thi, isliye block उसी speed se nikalta hai jिससे aaya tha (reversed direction mein). Speed gain karna energy conservation violate karega.
SE5. "Wall case mein (ek single block of mass at speed jo wall-fixed spring se takraata hai) mujhe phir bhi common velocity dhundhne ke liye likhna chahiye."
Koi doosra free body nahi hai jiske saath momentum share ho, aur wall momentum ko non-conserved banata hai, isliye woh equation yahan meaningless hai. Sahi tool energy hai: .
SE6. "Kyunki dono masses se chhota hai, expected se kam energy store hoti hai — iska matlab energy lost hui."
Koi energy lost nahi hoti; sirf relative motion ke liye correct effective mass hai. "Missing" KE destroy nahi hoti — yeh drift KE hai jo kabhi store hone ke liye available hi nahi thi.
SE7. "Ek light block () jo heavier block se takraata hai woh kabhi backward nahi ja sakta, isliye negative final velocity ek galti hogi."
Ek light block heavier block se genuinely rebound karta hai; elastic result negative hota hai jab , aur minus sign sirf leftward matlab rakhta hai. Momentum aur energy dono check out karte hain, isliye rebound real hai.

Why questions

WQ1. Hum problem ko "collision phase" aur "compression phase" mein split kyun karte hain?
Kyunki alag forces alag timescales par dominate karti hain — huge, brief contact force ko momentum chahiye (impulse view), jabki slow, finite spring force ko energy chahiye. Ek law per phase, us force ke hisaab se choose karo jo negligible hai.
WQ2. Reduced mass kyun mein aata hai lekin mein kabhi nahi?
poore system ke drift ke baare mein hai, isliye total mass use karta hai; blocks ki relative squeezing ke baare mein hai, aur relative motion ek single body ki tarah behave karti hai jiska mass ho. Dekho Reduced Mass and Two-Body Problems.
WQ3. Hum poore spring encounter ko elastic kyun treat kar sakte hain bina kabhi coefficient of restitution compute kiye?
Kyunki "ideal spring saari stored energy return karti hai" hi restitution ka physical content hai; spring mechanism elastic result ko construction se guarantee karta hai.
WQ4. Maximum compression ka moment momentum conservation apply karne ke liye natural jagah kyun hai?
Us instant par dono blocks ek velocity share karte hain, ko ek single-unknown equation mein badal deta hai — problem ka sabse clean snapshot.
WQ5. Energy conservation ek ordinary (non-spring) inelastic collision ke dauran fail kyun hoti hai lekin poore spring encounter mein succeed karti hai?
Inelastic collisions KE ko heat/deformation mein convert karti hain (unrecoverable); ek ideal spring sirf KE borrow karti hai recoverable elastic PE ke roop mein aur sab wapas kar deti hai.
WQ6. Centre of Mass Frame mein problem dekhne se stored energy obvious kyun ho jaati hai?
Us frame mein total momentum zero hota hai, isliye max compression par sab kuch momentarily still hota hai aur frame ki saari KE — exactly — spring mein baith jaati hai.
WQ7. Max-compression formula same kyun hai chahe spring baad mein release ho ya latch ho jaaye?
Turning point tak compression phase physically dono cases mein identical hai; latching ya releasing sirf decide karta hai ki peak ke baad kya hoga, na ki squeeze kitna gehra gaya.

Edge cases

EC1. Agar ho (dono blocks saath move kar rahe hon) toh kya hai?
Zero — relative approach speed , isliye ; woh simply saath coast karte hain.
EC2. Spring stiffness hone par ka kya hota hai?
— infinitely stiff spring muskil se compress hoti hai, aur encounter ek instantaneous elastic bounce jaisi lagti hai.
EC3. Agar ho (target immovable, jaise wall) toh kya hoga?
aur , wall case recover hota hai: jisme block 1 ki saari KE stored hoti hai.
EC4. Agar two-free-block elastic result mein ho toh kya hoga?
Blocks velocities swap karte hain — incoming block dead stop ho jaata hai aur target par move off karta hai, kyunki .
EC5. Do blocks jisme spring block 2 ke front face se attached hai (toh contact sirf tab hoga jab block 1 catch up kare): agar woh apart start ho rahe hain, , toh kya hoga?
Kyunki block 1 peeche reh raha hai, uska face spring ke free end ko kabhi press nahi karta, isliye koi compression nahi hoti aur blocks simply unchanged drift apart ho jaate hain. (Agar spring dono blocks se glued hoti, toh apart move karna usse stretch karta — ek alag, tension problem jo is note se bahar hai.)
EC6. hone par (spring vanishingly soft), kya predict karta hai, aur kya yeh physical hai?
Mathematically , lekin yeh ek idealisation hai: ek real spring ki finite length hoti hai aur coils eventually touch karti hain (ya blocks collide karte hain), isliye formula sirf tab valid hai jab spring ideally behave kare. Practically, ek bahut soft spring matlab ek huge lekin bounded squeeze aur ek bahut gentle, slow interaction.
EC7. Agar blocks ki equal masses hon aur equal-but-opposite velocities hon () toh kya hai?
Zero — total momentum cancel hoti hai, isliye max compression par dono momentarily rest mein hote hain aur saari initial KE, , stored hoti hai (Centre of Mass Frame aur lab frame yahan coincide karte hain).

Recall One-line survival kit

MEME + Max squish = Same swish. Momentum during the Moment; Energy for the Expansion; aur deepest squeeze tab hota hai jab dono blocks same speed par swish karein. Is poore page ki har cheez inn do lines ka consequence hai.


Connections