*GraphicPair() - tire

Creates a pair of tire graphic statements.

Syntax

*Graphic(gr_name,"gr_label",TIRE, body, point_1, POINT|VECTOR, point_2|vector, tire_profile)

Arguments

gr_name
The variable name of the graphic entity.
Data type: varname
gr_label
The descriptive label of the graphic entity.
Data type: label
TIRE
This argument indicates that the graphic is of type tire.
body
The body or body pair associated with this graphic.
Data type: Body or Body Pair
point_1
A point or a point pair that specifies the location of the tire.
Data type: Point or Point Pair
POINT|VECTOR
A keyword that indicates the alignment method.
point_2|vector
An entity variable referring to a Point, PointPair, Vector, or VectorPair which is based on the above keyword.
Data type: Point, Point Pair, Vector, or Vector Pair
tire_profile
Tire and Rim Association (T&RA) specification.
Data type: string

Example

*BodyPair(b_wheel, "Wheel", p_wheel_cg)
*PointPair(p_wheel_cg, "Wheel cg")
*PointPair(p_splign, "Spindle align point")
*GraphicPair(g_tire, "Tire",  b_wheel, 
                              p_wc, 
                              POINT, 
                              p_spalign, 
                              P215/70*15)

Context

*BeginMdl()

*DefineAnalysis()

*DefineGraphic()

*DefineSystem()

Comments

When point_2 is used instead of a vector, the axis of the tire is defined by the vector passing through point_1 and point_2.

Supported tire sizes for graphics.

To avoid the graphic being visible during MotionSolve result animation in HyperView, set the hide_in_post attribute to {{true}}. For example: *Set(gra_link.hide_in_post, true). This option will set the graphic component's visibility to be turned off when the result H3D is loaded in HyperView.