Hi Philip,
In Simscape Multibody, the initial conditions for velocities are typically set at the joint level, and these conditions propagate through the connected bodies. If you set an initial velocity at the first joint, it's expected that this velocity will influence all downstream bodies, as they are physically connected and thus will move together unless acted upon by other forces or constraints.
If you're trying to model a bolas, where two weights are connected by a string or chain and thrown with one weight leading, you might be encountering the issue because in the physical world, the trailing mass would not immediately have the same velocity as the leading mass due to the slack in the connection.
To model this more accurately, consider the following adjustments:
- Instead of using a rigid joint between the masses, use a flexible connector that can simulate a rope or chain. This could be a spring-damper system that allows for some stretch and lag in the response of the second mass.
- Instead of applying the initial velocity to the joint, apply it directly to the first mass. You can use the setInitial command in Simscape to set the initial conditions for velocities of the bodies.
- If you need to use a joint to connect the two masses, you can use a massless body (or a very small mass) as the connector. This body would not significantly affect the dynamics but would allow you to apply different initial conditions to each mass.
- You can use sensors to measure the state of the system and actuators to control the velocities independently if needed. This might be more complex and require control logic, but it can give you the exact behavior you want.
- If the standard joints do not provide the behavior you need, you can create a custom joint using Simscape language that has the specific constraints and initial conditions you require.
