MotionView User's Guide

Sinusoidal Steering

Sinusoidal Steering

Previous topic Next topic Expand/collapse all hidden text  

Sinusoidal Steering

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Introduction

A Sinusoidal steering event simulates a vehicle driving at a constant speed while a sin wave input is applied to the steering wheel.  The event is used to simulate the On-center steering test described in SAE paper 840069.  Standard vehicle outputs are included in the event.  Body state variable output requests (displacement, velocity, acceleration) are included in the body system and tire output is included in the Tire System.  A plot template is available to plot the results.

sinusoidal_steering_event_example_mv

Sinusoidal Steering Event

sinusoidal_steering_event_example_top_view_mv

Top View of a Sinusoidal Steering (Vehicle is Extremely Small)

Detailed Description

The Sinusoidal steering event is designed to work with a full vehicle model that has been built through the MotionView Assembly Wizard.  The event should attach to the model automatically when added through the Task Wizard.  The event can be used with models built manually, as long as the attachment scheme in the event is strictly followed.

The event is conducted to determine the vehicle response to the steering wheel input from a low frequency sin wave.  The event simulates the performance of the vehicle in the under a 0.2G lateral event and is used to characterize the steering feel for driving events where the vehicle needs to be precisely controlled.  The event should predict steering feel for the vehicle in normal highway events at moderate lateral acceleration (under 0.3G).

The values for the initial Vehicle velocity, Steering input magnitude, and Steering input frequency can be modified via the event Form (shown below).

task_wzd_dialog_sinusoidal_steering_event_mv

Sinusoidal Steering Data Dialog

The entities in the event are displayed in the MotionView Project Browser as shown in the image below:

sinusoidal_steering_browser_mv

Project Browser View - Forms - Sinusoidal Steering Analysis

Nine types of modeling element containers (Datasets->templates) are used to define the event (see below).  Two sub-systems (a Drive torque controller and a marker for the request) are also included in the event.

hmtoggle_plus1Attachments

The event uses the standard event attachment.  The attachments resolve automatically if the model is built through the Model Wizard.  The attachments contain the minimum data the event needs to run the analysis.  The attachments are standard for most events.

events_attachment_list_mv

Sinusoidal Steering Event – Attachments

hmtoggle_plus1Curves

A single curve is included in the Sinusoidal steering event.  The curve is not used by the event but is included in case you want to switch to an event that is driven on a path.

sinusoidal_steering_browser_curves_mv

Project Browser View - Curves - Sinusoidal Steering Analysis

hmtoggle_plus1Datasets

One dataset is used in the system, which contains the data used to describe the Sinusoidal steering event.  The event allows you to set the initial vehicle velocity, lane width, steering input magnitude and steering input frequency.  The wheel rotational velocities and ground height (shown with a blue background) are calculated values and should not be changed.

sinusoidal_steering_browser_dats_sets_mv

Project Browser View - Datasets - Sinusoidal Steering Analysis

sinusoidal_steering_dats_sets_panel_dialog_mv

Dataset Property Data Dialog - Sinusoidal Steering Analysis

hmtoggle_plus1Forms

The Form is the only place that you should change the Sinusoidal steering event.  Vehicle velocity, Steering input magnitude and Steering input frequency are the parameters that can be modified.  You can edit the event template if you want to make the event run longer.

sinusoidal_steering_browser_forms_mv

Project Browser View - Forms - Sinusoidal Steering Analysis

sinusoidal_steering_forms_panel_dialog_mv

Sinusoidal Steer Data Analysis - Form Dialog

hmtoggle_plus1Graphics

Seven graphics are defined in the event.  The graphics define the cones and the straight road graphics and should not require any user input.

The straight road graphics are included to illustrate the path being driven and are defined parametrically using the data in the Sinusoidal steering Form.  Straight road graphics should never require editing unless the event is being fundamentally changed.

sinusoidal_steering_browser_graphics_mv

Project Browser View - Graphics - Sinusoidal Steering Analysis

sinusoidal_steering_event_cone_graphics_example_mv

Cone Graphics

sinusoidal_steering_event_straight_road_graphics_example_mv

Straight Road Graphics

hmtoggle_plus1Joints

A ball joint is included in the Sinusoidal steering event.  The joint attaches a dummy body to the steering rack.  The joint is included to make certain events work in ADAMS.  Attach the dummy body to the steering rack if building a model manually.

sinusoidal_steering_browser_joints_mv

Project Browser View - Joints - Sinusoidal Steering Analysis

events_joints_ball_joint_panel_example_mv

Joints Panel - Sinusoidal Steering Analysis

hmtoggle_plus1Markers

Five markers are included in the Sinusoidal steering event.  The path origin is the origin of all graphics and is parametrically defined to be the CG of the vehicle body.  The markers refer to points and the points contain the parametric logic.

The path outline markers point to the path outline points for their XYZ location.  The markers are used to define the road graphics.  None of the markers should require any user input.

sinusoidal_steering_browser_markers_mv

Project Browser View - Markers - Sinusoidal Steering Analysis

hmtoggle_plus1Motions

Three motions are included in the event.  The steering motion is used to steer the vehicle and acts on a revolute joint that connects the steering column to the vehicle body.  If a steering column is not included in the model, the motion acts on a joint between the steering rack input shaft and the vehicle body.

The Front and Rear Wheel Motions act on the wheel spindle revolute joints connecting the wheel hub to the knuckle.  The motion is initially zero (fixing the wheels to the knuckle) so the model converges statically.  After static analysis, the wheel locking motions are deactivated to allow the tires to rotate during the dynamic analysis.

sinusoidal_steering_browser_motions_mv

Project Browser View - Motions - Sinusoidal Steering Analysis

hmtoggle_plus1Points

Fifteen points are defined in the Sinusoidal steering event.  All points are used to create the road graphics and cone graphics used to illustrate the road.  The points contain parametric logic to define their X, Y, and Z locations.  You should not need to modify any points.

sinusoidal_steering_browser_points_mv

Project Browser View - Points - Sinusoidal Steering Analysis

hmtoggle_plus1Templates

A template is included in the Sinusoidal steering event task.  The template is solver specific, and only the MotionSolve template is documented.  The template is inserted in the solver deck after the </Model> command and controls the execution of the event.

The steering wheel motion is modified in the template to use the values found in the dataset.  The event end time (default is 6 seconds) is set in the template and should be modified to simulate a complete on-center steering test.

sinusoidal_steering_browser_templates_mv

Project Browser View - Templates - Sinusoidal Steering Analysis

The template for this event is shown below:

<ResOutput

    angle_type          = "YPR"

 />

 <ResOutput

    mrf_file            = "TRUE"

 />

 <ResOutput

    plt_file            = "TRUE"

 />

 <H3DOutput

    switch_on           = "TRUE"

    increment           = "1"

 />                  

{if (tire_dataset.opt_omega.ival ==1)}

<!--Initial static analysis -->

 

<Simulate

 analysis_type = "Static"

 end_time      = "0.0"

/>        

{endif}

<Deactivate

 element_type = "MOTION"

 element_id = "{mot_frnt_wheel.l.idstring}"

/>

<Deactivate

 element_type = "MOTION"

 element_id = "{mot_frnt_wheel.r.idstring}"

/>

<Deactivate

 element_type = "MOTION"

 element_id = "{mot_rear_wheel.l.idstring}"

/>

<Deactivate

 element_type = "MOTION"

 element_id = "{mot_rear_wheel.r.idstring}"

/>

{if (tire_dataset.opt_omega.ival ==2)}

<!--Initial static analysis -->

 

<Simulate

 analysis_type = "Static"

 end_time      = "0.0"

/>        

{endif}

<Deactivate

 element_type = "JPRIM"

 element_id = "{j_clamp_1_body.idstring}"

/>

<Deactivate

 element_type = "JPRIM"

 element_id = "{j_clamp_2_body.idstring}"

/>  

 <Motion_Joint

    id                  = "{wh_motion.idstring}"

    expr                = "-{ds.str_mag.value}D*SIN(2*PI*{ds.str_freq.value}*TIME)"

 />                              

                               

<Simulate

     analysis_type       = "Transient"

     end_time            = "6"

     print_interval      = "0.05"

 />

 

<Stop/>

References:

SAE 840069 – Objective Evaluation of On-Center Handling Performance.