Skip to content

Commit 10acfea

Browse files
committed
Initial commit R2016a.
1 parent 2784837 commit 10acfea

12 files changed

+35
-0
lines changed

Cylinder_Lift.slx

-39.6 KB
Binary file not shown.

Hinge_Hard_Stop.slx

-23 KB
Binary file not shown.

MS2G_SS_Intf_Lib.slx

7.67 KB
Binary file not shown.

Motor_Slider_Crank.slx

-24.7 KB
Binary file not shown.

Motor_Slider_Crank_Hardstop.slx

-25.7 KB
Binary file not shown.

Motor_Slider_Crank_x2.slx

-27.7 KB
Binary file not shown.

README.txt

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
Connecting Simscape 1-D mechanical models and 3D models in Simscape Multibody.
2+
3+
4+
This file contains example models showing how to connect 3D and 1D mechanical models.
5+
Connecting the models using Simscape Physical Signals ensures a lossless transfer
6+
of mechanical power between the two systems. This submission contains a library
7+
that contains the interface blocks (rotational, translational), and example models
8+
showing how to use them.
9+
10+
You need to ensure that your use of this interface is physically valid. Connecting
11+
a 3D mechanical model to a 1D mechanical model requires that you follow a few basic
12+
rules:
13+
14+
15+
1. Never add inertia directly to the node on the Simscape side of the interface.
16+
17+
All masses in Simscape models live in an implicit inertial reference frame. A Simscape mechanical
18+
circuit interfaced to a Simscape Multibody machine in general moves in an accelerated frame. A simulation
19+
with such a circuit does not include the pseudoforces acting on the Simscape mass and inertia elements
20+
as experienced in such a noninertial frame and thus violates Newton's second law of mechanics.
21+
22+
2. If you must model inertia in the Simscape network, connect it to the interface element
23+
via a spring and damper connected in parallel. Be aware that a Simscape circuit does not model
24+
the motion of such bodies along or about axes orthogonal to the coupled primitive axis chosen
25+
in the interfaced Joint.
26+
27+
3. Quantities sensed in Simscape (like translation at a node) may be offset from comparable quantities
28+
measured in Simscape Multibody. This is because the initial position of the Simscape Multibody joint,
29+
which is determined during the assembly process, is not automatically conveyed to the Simscape network.
30+
Once you know this value (after updating the diagram), you can enter it into the Simscape network.
31+
32+
33+
34+
Copyright 2013-2016 The MathWorks, Inc.
35+

sm_ssci_hinge_hardstop.slx

27.8 KB
Binary file not shown.

sm_ssci_hydraulic_lift.slx

45.6 KB
Binary file not shown.

sm_ssci_motor_slider_crank.slx

28.7 KB
Binary file not shown.

0 commit comments

Comments
 (0)