+$#>Lotus Suspension Analysis – SHARK,  Introduction

Lotus Suspension provides a simple to use tool for the design and analysis of suspension geometry. Standard suspension types using individual default pre-filled templates provide easy creation of kinematic models in either 2D or 3D modes.

{bmc bm0.bmp}
Creating a new model using pre-defined template types

Analysis of suspension geometry in Bump, Rebound, Roll and Steering is performed in an interactive environment. Graphical plots of selected derivatives are continually updated as suspension hard points are modified, either singly or as groups.

{bmc bm1.bmp}
Graphical Display of Suspension Model

The inclusion of bushes, spring properties, tyre stiffness and external forces allow compliant response to be calculated, including automatic creation of ‘compliance coefficients’ for defined load sets.

{bmc bm2.bmp}
Compliant Suspension Coefficients Display

Mass properties and component damping provide modal analysis capability and the prediction of the forced damped response of the system. Individual mode shapes can be viewed animated on the model. The forced response at specific frequencies can be animated together with the complete speed sweep response.

{bmc bm3.bmp}
Modal Analysis Frequencies – Bar Chart

Suspension templates can be either corner models or complete axle models. These complete axles may be because they are rigid axle suspension types or because it is required to model the effect of a connecting link such as the rack, sub-frame or an anti-roll bar.

{bmc bm4.bmp}
Example Full Axle Template – Anti-Roll Bar

+$#>Overview - Introduction

Shark provides an analysis tool for calculating the suspension derivatives of pre-defined types of kinematic suspensions, through an interactive graphical interface. The program calculates the suspension derivatives, i.e. camber, castor, toe angle, roll centre height, etc., over three individual or mixed articulation types, bump/rebound, roll and steering, (steering 3D module only).

It functions either in 2D or 3D forms with increasing level of data requirements and analysis results with the 3D form. All suspension hard points can be edited or dragged through a fully dynamic 3D viewing environment with graphical results updated as the suspension hard points are modified.

Extensions to the integral solver allow for bush compliant effects and applied external forces to be included to understand the impacts of compliance on the suspension characteristics.

Mass and damping properties also allow for the rigid body modes to calculated and the modal shapes viewed. The application of spring forces and external forces allow the forced/damped response to be predicted and the displacements viewed at user defined frequencies.

{bmc bm5.bmp}
Example screen shot – Overall appearance of application

+$#>Overview, Modules

The program has two modules, 2D and 3D. The suspension geometry data used in each module is completely independent of the other module. Switching between modules with the relevant menu or icon will change the display to reflect the model, results and settings of that module.

It is possible to move a 2D model data into one of the default 3D templates via the Solve / Convert 2D to 3D menu option. You currently cannot automatically simplify 3D data down to 2D, this not considered a likely requirement.

Many of the commands and menu options are identical between the 2D and 3D modules. Where a menu or action is not relevant to that module it will be ‘greyed’ out.

Again where possible the same functionality and behavior is common between the 2D and 3D modules.

The 2D module works in the cross car plane only, i.e. Y-Z plane, where Y is cross car and Z is height.

{bmc bm6.bmp}
Module Icons in the File toolbar

A range of displacement ‘modules’ are available. In 2D mode displacement can be in either Bump/Rebound or Roll. In 3D mode displacement can be in Bump/Rebound, Roll, Steer or Combined Motion. All Bump/Rebound motion options can be applied as moving ground or moving body. The 3D combined motion mode allows combinations of bump, roll and steer displacements to be applied to the model.

Bump/Rebound displacement is defined by the vertical displacement (Z direction) of the body (or the ground plane).

Roll displacement is defined by the angle of roll of the vehicle body about the original roll centre axis.

Steering displacement for the default steering rack is defined by the horizontal displacement (Y direction) of the inner track rod ball joint. With the option of a steering box, displacement is the angular rotation of the steering arm.

The combined mode can mix any of the above three displacements at each calculation position. The bump motion can be different for each wheel.

{bmc bm7.bmp}

All modules have ‘Standard’ and ‘Extended’ forms. For 3D in ‘Standard’ form you specify the displacement limit and the step size, whilst in ‘Extended’ form you specify the number of positions and the displacement value at each position.

Note that Vertical displacement modules have separate Bump and Rebound limits and step size for the ‘standard’ form, whilst Roll and Steer modules have a single limit and step size which is mirrored for both +ve and –ve directions. In extended mode the bump/rebound travel is entered as either a positive (for bump) or a negative value (for rebound).

+$#>Overview – 2D Suspension Types

In the 2D module there are only two basic suspension types;

1) Double Wishbone
2) Macpherson Strut

Because in the 2D module no provision is included for the modeling of springs, dampers or steering mechanisms, the majority of the 3D module’s templates are covered by the two 2D suspension types.

This does mean that trailing arm type suspensions cannot be modelled in the 2D module.

The 2D module works in the cross car plane only, i.e. Y-Z plane, where Y is cross car and Z is height.

{bmc bm8.bmp}
Selecting the 2D Suspension Type

+$#>Overview – 3D Suspension Types

The 3D module has 30 pre-defined suspension types;

 1) Double Wishbone, damper to lower wishbone 
 2) Lower H frame, single upper link
 3) Steerable Macpherson Strut
 4) Non-Steerable Macph Strut, two lower ball joints, tie to ground
 5) 5-Link Rigid Axle (Panhard Rod)
 6) Double Wishbone, damper to upper wishbone
 7) Non/Steerable Macpherson Strut, steering arm to lower wishbone
 8) 4-Link Rigid Axle (Panhard Rod)
 9) 4-Link Rigid Axle (Twin Upper)
10) Trailing Arm with Two Cross Car Links
11) Semi/Trailing Arm
12) Steerable Twin Parallel Wishbones with Steering Knuckle
13) Double Wishbone, Damper to Knuckle
14) Double Wishbone with Push Rod Suspension
15) Double Wishbone, Rocker Arm Damper
16) Non/Steerable Lower ‘A’ Arm with Toe Link
17) Double Wishbone, Push Rod, Mono-shock
18) Double Wishbone, Upper Toe Link, Drop ‘S’ Link
19) Hinged Trailing Arm, Twin lower Link
20) Double Wishbone, Twin Outer Ball Joints
21) 5-Link Rigid Axle (Watts Linkage)
22) Double Wishbone, Twin Outer Ball Joints, Spring Front
23) Double Wishbone, Anti-Roll Bar
24) Steerable Macpherson Stut, Twin Outer Ball Joints
25) Double Wishbone, Twin Lower Outer Ball Joints
26) Double Wishbone, Damper to Lower Wishbone, Compliant Rack
27) Steerable Macpherson Strut, Twin Lower Link
28) 4-Link Rear, Transverse Control Link
29) Twist Beam – Twin Wheel
30) Generic 5-link Rear

Some of these suspension types are steerable and in which case will appear as options for both front and rear suspension selections. Whilst non-steerable suspension types will only appear in the rear suspension list. The majority of these templates are just corner models, some axle templates are included. Users can convert these or their own corner templates to axle templates using the menu item ‘Edit / Convert Corner to Axle Model’.

For steerable suspension types the steering mechanism type is selected separately from either a rack or steering box.

{bmc bm9.bmp}
Selecting the 3D Front Suspension Type

It is possible to define your own 3d templates. These can be loaded automatically and either used as additions to the existing hard coded templates, replacements for or modifications of the hard coded ones. Templates that are loaded automatically are referred to as ‘default’ templates. Users can also load additional ‘user’ defined templates by browsing for an external file. All templates loaded from external files, (i.e. both default and user), are loaded into a certain template index. Thus it is possible to overwrite an existing hard coded template with a default or user template having the same index number. Similarly it is possible to overwrite a default template with a user template. The default templates are stored in a text file named ‘_User_Templates.Dat’ and is searched for in the programs startup folder. It is scanned for a program start-up and if found it is read and any extra templates loaded.

It is possible to re-run the defaults loading process during a session, (without the need to restart), by using the menu item File / Re-Read Default Templates.

+$#>Overview – 3D Steering Types

The 3D front suspension templates are restricted to being ‘steerable’. A steerable template has an identified point attached to the body that is articulated in a prescribed manner for the Steering ‘mode’ of analysis.

Two types of steering type are available;

1) Steering Rack
2) Steering Box (two types)

The steering rack applies a linear displacement of the nominated track rod end along the Y-axis. Note that if the rack is used in an asymmetric suspension and the two rack, inner track rod points are positioned at different x-positions the rack motion is along the line defined rather than pure y-axis linear motion. No additional data points are required to define the steering rack. The defined steering travel is the linear distance in mm.

The steering box type requires additional geometry points to be added to identify the pitman point and steering arm axis. The defined steering travel for a steering box type is angular rotation of the steering arm. Two steering box types are available, (illustrations of each type are given below).

{bmc bm10.bmp}
Steering box graphical display – Box points highlighted

Note that steering is not considered in the 2D module as it is by definition a 3D phenomena.

{bmc bm11.bmp}
Selecting the 3D Steering Articulation Type

The two steering box types are illustrated below. The number of data points are the same but the implied mechanism is different.

{bmc bm12.bmp}
Steering Box Type 1

{bmc bm13.bmp}
Steering Box Type 2

+$#>Overview – Graphical Interface

The graphical interface consists of a conventional Windows style container window, with a top menu bar and a series of status panels along the bottom.

Optional toolbars are drawn by default to the left of the window, containing short cut icons to some of the main menus. The user can specify the visibility of the toolbars together with their position. Additionally the toolbars can be displayed as ‘floating’ rather than anchored to one of the edges.

Floating toolbars can be re-docked to the required edge through picking and dragging to the new position, (note the outline shape will change to indicate docking).

The initial positions of the toolbars can be set via the SetUp / Start Options / Default ToolBar Position menu item, with Top, Bottom, Left or Right options available. This change is saved to the users ‘ini’ file and will be applied next time the application is re-started. Note that with the introduction of individual user toolbar settings, each toolbar can have its own start position and this setting is only used for the initial definition process.

{bmc bm14.bmp}
Confirming the change in toolbar position

The suspension graphics is drawn in the window titled ‘2D Display’ or ‘3D Display’ as appropriate for the current module setting. This window cannot be closed, but can be repositioned, re-sized and minimized. Only one graphic window can be opened by the application at a time, (i.e. you cannot open different models at the same time using different graphic windows in the way that a multi-document application like Word would).

{bmc bm15.bmp}
Example 2D Graphic window

Results graphs are displayed in individual windows. Each new graph added opening a new window. The graph windows can be moved, re-sized, closed and minimized. The title of the graph window reflects the plotted variable.

{bmc bm16.bmp}
Example 3D Graph window

By default on start-up only the graphic window and toolbars are drawn, no graphs are displayed until they are added via the Graph / New/Open menu.

The settings for window positions, sizes and variables can be saved such that when the application is re-started all windows are re-opened in the same positions, see Window / Save Def. Window Settings.

+$#>Overview – Hard Point Dragging

The suspension hard points can be selected from the screen via the mouse and ‘dragged’ to a new position, the suspension derivatives being re-calculated as the hard point is moved. The selected derivatives that are being displayed graphically are updated during the hard point screen dragging. Point dragging can be in a 2D view along both viewed axes, a single axis or dragging in a 3D view along a selected axis direction.

{bmc bm17.bmp}
Graphics Screen – Dragging mode, tracking lines show Y axis direction.

The majority of the point dragging functionality is performed using a combination of left and right mouse buttons. The mouse buttons are also used extensively for the dynamic viewing option and thus this ‘sharing’ requires a switch between ‘edit’ mode and ‘dynamic view’ mode.

Point dragging is one part of the ‘Edit’ mode. The other two parts are direct editing and joggle editing.

To indicate when the application is in ‘dynamic view’ mode and when in ‘Edit’ mode not only are the relevant menus and icons ‘checked’ but also ‘corners’ are added to the graphic display when in ‘dynamic view’ mode.

{bmc bm18.bmp}
Graphics Screen – Indicating in Dynamic View mode.

To change to editing mode un-select ‘dynamic viewing’ using View / Dynamic Viewing / Off. Alteratively select the dynamic viewing icon from the ‘view’ toolbar.

{bmc bm19.bmp}
Dynamic Viewing Icon- Shown as ‘on’.

When in point dragging mode ‘tracking lines’ are drawn to indicate the current ‘tracking’ direction(s). To change the current tracking direction the right mouse button will cycle through the available tracking direction options. A similar action is achieved by selecting the mouse icon from the ‘view’ toolbar.

{bmc bm20.bmp}
Mouse Icon – Cycles through tracking options.

Selecting any of the ‘Edit icons’ changes the mode to edit and cancels the dynamic view mode. In a similar way selecting any of the three dynamic view icons changes to ‘dynamic view’ mode.

Hard point joggling operates in a similar way to dragging with regard to available directions. The drawn joggle symbol indicates the number of joggle directions available. To use joggle select either Ctrl + Arrow Key for coarse joggle or Shift + Arrow Key for fine joggle. The joggle fine size is a tenth of the coarse size, the coarse size can be set via SetUp / Gen Defaults…

{bmc bm21.bmp}
Example Screen shot of point joggle

Point dragging is affected by both Groups and Coincident points. The settings for groups and point coincidence change a single point pick and drag event into a potential single point pick but multiple point drag. In the case of groups, the current groups points are all translated by the same amount. Whilst for point coincidence only the point or points selected from a displayed list are moved, again all selected points are moved by the same amount.

{bmc bm22.bmp}
Example Coincident point pick

The coincident point selection feature is switched on via the Edit / Point Coincidence Pick menu. When switched off the nearest point to the picked position is always selected. The tolerance used to decide whether two points are coincident can be changed via the SetUp / Gen Defaults… menu. A similar tolerance exists to control whether a point is within the pick region.

The default/standard method of model change during point dragging is to modify the position of a particular point, (or points for the case of a group), to its new position and hence change its relative position to any other point on the same part that hasn’t been dragged. This ‘change’ mode is referred to as ‘Change Part Lengths’. An alternative ‘change’ mode has been added that allows the existing part geometry to be retained. In this ‘Retain Part Lengths’ mode only the hard points attached to the body (i.e. ground) can be selected and dragged, but when dragged all part lengths and hence point relevant positions are retained on each part in the model.

A point may also be dragged along a user defined vector in either the ‘change point’ or ‘retain part’ methods.

The default tracking style is Linear. That is along the specified direction. In addition both spherical and circular methods are available, where the dragged point is projected back on to a defined sphere or defined circular arc.

+$#>Overview – Groups

In the 3D mode the hard points can be formed into groups such that when one of that group is selected via the mouse and ‘dragged’, the other points in the group are dragged by the same amount, i.e. maintaining their relative positions within the group. This can be used for example to mimic moving a wishbone or suspension upright.

The only visible change to the graphic display when in group mode is that the number of ‘pickable’ points is reduced to those in the group. Pickable points are drawn in a different colour and size to the non-pickable ones, (this can also be seen normally on static position versus incremental position, where only the static position can be picked). A further indicator as to the active use of a group is when in edit mode the drag lines are only drawn through the current groups’ points.

{bmc bm23.bmp}
Group Selected – Lower Wishbone Points Grouped

The user can define any number of groups, a single point can be a member of any number of groups. Only one group can be current at a time. The group relationship is thus only applied when the group is current and the relationship taken from the point of making the group current.

Group data is saved with the model data file for subsequent re-use. Individual groups can be deleted from the model using Edit / Groups / Delete selecting the required group to delete by its label.

Users can create groups using the Edit / Groups / Create... menu item. Give the new group a unique label when prompted. A group is associated with either the front or rear suspension, you cannot add points to one group from both ends. Creating a group thus involves identifying how many points and which points are associated with the group.

{bmc bm24.bmp}
Group Creation – Selecting the required points for a three point group

The contents of an existing group can be edited through the Edit / Groups / Edit menu.

Once a group has been created it has no effect on hard point editing until the group is made current. To make a group current select the required group from the Edit / Groups / Current menu.

{bmc bm25.bmp}
Making a Group Current

To revert back to conventional data editing with all hard points available ‘cancel’ the group setting using the Edit / Groups / Cancel menu item.

A temporary group can be created by the selection of a screen area, the created group will include all points within this selected region. A temporary group created in this way is disabled/canceled in the same way as a conventional group, but once canceled is then lost and would need to be re-created if required again. 

+$#>Overview – Dynamic Viewing

The main graphical window has dynamic viewing via the mouse, that allows translation, scaling and rotation (3D module only), of the suspension graphics.

Dynamic viewing shares the functional use of the mouse and its buttons with the hard point data editing, joggling and dragging functions. Thus to enable both dynamic viewing and editing to use the mouse you switch between the two modes. The ‘dynamic view’ icon together with the associated menus indicate the status of these two modes, when checked the application is in dynamic view mode and the mouse and its buttons can be used to perform translation, scaling and rotation of the graphics model. Additionally the graphic display has symbols drawn in each corner as a visual indication that the application is in dynamic view mode.

{bmc bm26.bmp}
Dynamic Viewing – Indicators marked

The dynamic view mode has three options, (two in 2D), being Translation, Scaling and Rotation. Each of these options has its own icon and menu item, View / Translate View, View / Scale View  and View / Rotate View. Selecting any of these options will enable dynamic viewing (if in data editing mode), or just change dynamic view type, (if already in dynamic view).

{bmc bm27.bmp}
Dynamic Viewing – View Type Icons

The dynamic view modes use the motion of the mouse between key down and key release to change the view. The translate view mode simply follows the translation of the mouse within the current view plane. The Scale view mode uses the mouse vertical position to scale the current view plane. Moving the mouse up scales the view out, (i.e. model appears further away), whilst moving the mouse down scales the view in.

The rotate dynamic view, (only available in 2D), has two actions depending on the position of  initial mouse selection point. Selecting towards the middle of the image will rotate the line of sight, whilst selecting towards the edge of the view will rotate the view around the line of sight only.

When in dynamic view mode the right mouse button will cycle through the available dynamic view options.

+$#>Overview – 2D Module

The 2D mode works with reduced hard points, i.e. no springs, dampers, pushrods etc., and is in the cross car view only (Y-Z plane). Construction lines are drawn to show instantaneous centres and kinematic roll centre positions. The user can define the required bump/rebound and roll camber, the bump/rebound and roll centre height and the roll centre lateral motion with roll angle. These are compared on the graphs to the current hard points actual solution or with one of the hard points ‘freed off’ are used to illustrate on the suspension graphical display the point location that meets the derivative targets.

Note that steering is not considered in the 2D module as it is by definition a 3D phenomena.

{bmc bm28.bmp}
2D module graphics display

In most respects the functionality of the 2D module follows that of the 3D module in-terms of windows, graphics and graphs. Where relevant to the 3D module only features and menus will be disabled.

The 2D module is intended to be a simplified analysis approach with both a reduced variable set and a reduced results set. Its restriction to the cross car plane means that it can not be applied to trailing and semi-trailing type suspensions.

The 2D module has only two basic suspension types, Double Wishbone and Macpherson Strut.

{bmc bm29.bmp}
2D Module template types – New model menu

The 2D module can be used as a simplified route to a full 3D module. Once you have achieved your required 2D characteristics use the convert to 3D option, Solve / Convert 2D to 3D, to produce a fully populated 3D single axle model.

Within the 2D module you can use conventional hard point editing, joggling and dragging techniques to modify the suspension derivatives. This the default 2D solve mode as is referred to as ‘Fix All’, (Solve / 2D Fix Option / Fix All). In this Fix mode the suspension is fully defined/constrained and the displayed results are as constrained by the 2D mechanism. A range of alternative Fix modes are available where one of the hard point constraints can be ‘Freed’ up to allow the required camber curve and roll centre height to define the suspension. These ‘required’ curves must be defined through the relevant graphs ‘User Line’ data, (use the right mouse menu on the graphs to Edit User Line….).

The various available ‘Fix’ modes are set via the Solve  / 2D Fix Option sub menu.

In the 2D module the point dragging has been extended to include selecting the Kingpin Axis point and changing its angle, selecting the ground offset point to change the Kingpin offset at the ground plane and selecting the tyre contact point to drag and change the track.

{bmc bm30.bmp}
2D Module – Example Double Wishbone Top Outer ‘Free’

+$#>Overview – 2D Suspension Derivatives

The 2D suspension calculated derivatives for bump/rebound articulations are;

1) Camber Angle
2) Roll Centre Height
3) Track Change

Whilst for 2D roll articulation the calculated derivatives are;

1) Camber Angle
2) Roll Centre Height
3) Roll Centre Lateral

All other suspension derivatives are either fixed, (such as Kingpin Angle), or not applicable to the 2D module, (such as toe angle).

{bmc bm31.bmp}
2D Sample Graph – Includes User and Scope lines

+$#>Overview – 3D Suspension Derivatives

The 3D mode has four articulation types, bump/rebound, roll, steering and a combined mode. The combined mode allows the user to define a path of combined bump, roll and steering to enable wheel envelopes to be established. The suspension derivatives calculated are split into seven groups;

1) Standard
Wheel Travel (mm)
Camber Angle (deg) 
Toe angle (Plane definition) (deg)
Toe Angle (SAE definition) (deg)
Castor Angle (deg)
Kingpin Angle (deg)
Damper 1 Ratio (-)
Spring 1 Ratio (-)
Anti Dive (%)
Anti Squat (%)
Half Track Change (mm)
Wheel base Change (mm)
Damper 1 Travel (mm)
Spring 1Travel (mm)
Ackermann (%)
Castor Trail (hub) (mm)
Castor Offset (grnd) (mm)
Kingpin Offset (at wheel centre) (mm)
Kingpin Offset (at ground) (mm)
Mechanical Trail (mm)
Roll Centre Height to Body (mm)
Roll Centre Height to Ground (mm)
Handwheel Angle (deg)
Roll Angle (deg)
Steer Travel (mm) or (deg)
Position (pseudo time)
Bump Stop 1 Travel (mm) 

2) Positional
Roll Centre X (mm)
Roll Centre Y (mm)
Roll Centre Z (mm)
TCP X (mm)
TCP Y (mm)
TCP Z (mm)
Hub Centre X (mm)
Hub Centre Y (mm)
Hub Centre Z (mm)
Castored TCP X (mm)
Castored TCP Y (mm)
Castored TCP Z (mm)
Castor Intersect X (mm)
Castor Intersect Y (mm)
Castor Intersect Z (mm)
KPI Normal X (mm)
KPI Normal Y (mm)
KPI Normal Z (mm)

3) Extended
Tyre Vertical Force (N)
Swing Arm Length (Front) (mm)
Swing Arm ctr Y (Front) (mm)
Swing Arm ctr Z (Front) (mm)
Swing Arm Length (Side) (mm)
Swing Arm ctr X (Side) (mm)
Swing Arm ctr Z (Side) (mm)
TCP dX/dZ Gradient (mm/mm)
Damper 2 Ratio (-)
Spring 2 Ratio (-)
Damper 2 Travel (mm)
Spring 2Travel (mm)
Spring 1 Force (N)
BumpStop 1 Force (N)
Spring 2 Force (N)
BumpStop 2 Force (N)
Turning Circle Radius (mm)
Rack Axis Force (N)
Handwheel Moment (N.mm)
Steering Tie Rod Angle (deg)
Roll Steer Coefficient (%)
Roll Camber Coefficient (%)
KPI Length (mm)
Inner Drive Shaft Angle (deg)
Outer Drive Shaft Angle (deg)
Drive Shaft Length Plunge (mm)
Swing Arm Ctr X {FRONT} (mm)
Swing Arm Ctr Y {SIDE} (mm)
BumpStop 2 Travel (mm)
Opposite Toe Angle (Plane) (deg)
Opposite Toe angle (SAE) (deg)
Ackermann Delta (deg)
Ackermann Average (deg)
Ackermann Error (deg)
Ackermann (%)
Opposite Tyre Vertical Force (N)
Opposite Camber angle (deg)

4) Derivative d/dz
d/dz Camber Angle (deg/mm) 
d/dz Toe angle (Plane definition) (deg/mm)
d/dz Toe Angle (SAE definition) (deg/mm)
d/dz Castor Angle (deg/mm)
d/dz Kingpin Angle (deg/mm)
d/dz Half Track Change (mm/mm)
d/dz Wheel base Change (mm/mm)
d/dz Damper 1 Travel (mm/mm)
d/dz Spring 1Travel (mm/mm)
d/dz Castor Trail (hub) (mm/mm)
d/dz Castor Offset (grnd) (mm/mm)
d/dz Kingpin Offset (at wheel centre) (mm/mm)
d/dz Kingpin Offset (at ground) (mm/mm)
d/dz Mechanical Trail (grnd) (mm/mm)
d/dz TCP X (mm/mm)
d/dz TCP Y (mm/mm)
d/dz TCP Z (mm/mm)
d/dz Hub Centre X (mm/mm)
d/dz Hub Centre Y (mm/mm)
d/dz Hub Centre Z (mm/mm)
d/dz Damper 2 Travel (mm/mm)
d/dz Spring 2Travel (mm/mm)
d/dz Damper 1 Ratio (1/mm
d/dz Spring 1 Ratio (1/mm)
d/dz Damper 2 Ratio (1/mm)
d/dz Spring 2 Ratio (1/mm)
d/dz KPI Length (mm/mm)
d/dz Drive Shaft Length Plunge (mm/mm)
d/dz Castored TCP X (mm/mm)
d/dz Castored TCP Y (mm/mm)
d/dz Castored TCP Z (mm/mm)

5) Integral §dz
§dz Camber Angle (deg.mm) 
§dz Toe angle (Plane definition) (deg.mm)
§dz Toe Angle (SAE definition) (deg.mm)
§dz Castor Angle (deg.mm)
§dz Kingpin Angle (deg.mm)
§dz Half Track Change (mm.mm)
§dz Wheel base Change (mm.mm)
§dz Damper 1 Travel (mm.mm)
§dz Spring 1Travel (mm.mm)
§dz Castor Trail (hub) (mm.mm)
§dz Castor Offset (grnd) (mm.mm)
§dz Kingpin Offset (at wheel centre) (mm.mm)
§dz Kingpin Offset (at ground) (mm.mm)
§dz Mechanical Trail (grnd) (mm.mm)
§dz TCP X (mm.mm)
§dz TCP Y (mm.mm)
§dz TCP Z (mm.mm)
§dz Hub Centre X (mm.mm)
§dz Hub Centre Y (mm.mm)
§dz Hub Centre Z (mm.mm)
§dz Damper 2 Travel (mm.mm)
§dz Spring 2 Travel (mm.mm)
§dz Damper 1 Ratio (mm)
§dz Spring 1 Ratio (mm)
§dz Damper 2 Ratio (mm)
§dz Spring 2 Ratio (mm)
§dz KPI Length (mm.mm)
§dz Drive Shaft Length Plunge (mm.mm)

6) Graphic
	As relevant to the Model

7) User Defined
	As added/defined by the user

The derivatives can be viewed either individually through the results graphs, select Graphs / New/Open to open a new/additional graph or via the suspension derivative results file (SDF).

The variable actually displayed on the graph is best changed/set by using the right mouse button on the graph of interest and using the Y-Variable menu list.

{bmc bm32.bmp}
Graph Window – Showing right mouse button Y-variable menu selection

The SDF file can be displayed via the relevant icon or the Results / Formatted SDF menu. The SDF file can be displayed either as a user specified formatted list or as a set of spline coefficients or just as spline data. These last two have a collection of user definable settings that control which articulation types, which results and which ends are shown in the lists.

{bmc bm33.bmp}
Extract of the formatted SDF file display

All displayed graphs and SDF displays can be printed to produce hard copy records via the print menu options provided through the standard Windows® printer dialogues.

{bmc bm34.bmp}
Extract of the SDF splines display

+$#>Overview – Limit Boxes

For both modes, hard point ‘limit boxes’ can be switched on, theses boxes are set to allow only a user specified amount of travel in a specific direction. Thus when switched on, a point, (or a group point), cannot be dragged outside of its limit box. These boxes could perform one of two functions, firstly they could be set to represent packaging limitations, or secondly to indicate production tolerances. In the second case the program can run a tolerance analysis for the chosen hard point at all extremes of the limit box, the spread on the chosen derivatives is displayed on the current graphs.

The display of limit boxes have three settings, ‘On’, ‘Off’ but visible and finally ‘Off’ and invisible. There is no functional difference between the last two, it merely assists the clarity of the display by removing the additional graphical lines.

{bmc bm35.bmp}
3D Graphic Display showing Limit Boxes as On

The behavior and functionality of Limit boxes is identical between the 2D module and the 3D module with the obvious exception of the reduction of tolerances in only two dimensions.

To control the status of Limit boxes use the pull down menu Graphics / Point Limits  sub menu to set as Visible or to set as Use, (note that in this context use means ‘On’. Un-checking Use will turn limit boxes off but remain visible, whilst un-checking Visible will set limit boxes to ‘off’ irrespective of the current setting).

The first use of the ‘Limit Box’ is as a constraint on how far a hard points position can be moved in any direction whilst joggling or dragging.

If limit boxes are in use then you cannot ‘Joggle’ or ‘drag’ a point such that it is moved outside of the limit box. Limit boxes are defined as separate +/- distances in each of the three axes, (or two for the 2D module), i.e. a total of six values for the 3D module and four for the 2D module.

Note that it is still possible to edit a point to a position outside of the limit box even when limit boxes are ‘on’. In this instance the limit box is resized to accommodate the new position.

If limit boxes are not in use, (visible or not), when a points position is changed by any of the edit modes, (edit, joggle or drag), the limit box is enlarged if the new position falls outside the currently defined points limits.

Because of this individual point editing, each suspension hard point has its own ‘Limit Box’ dimensions. These can be individually re-set using the Data / Point Tolerances / Edit Point Tolerances… menu, identify the required axle and point, and finally edit the values.

{bmc bm36.bmp}
Selecting the single point prior to editing the limit box settings

To re-set the limit boxes for all point in one step, select Data / Point Tolerances / Set All Point Tolerances To… menu and edit the required values, (note that you do not need to enter the negative directions as a –ve value, this is assumed).

{bmc bm37.bmp}
Editing the point limit box for all points

The second use of the ‘Limit Box’ is as a design/manufacturing tolerance analysis tool. This is used in conjunction with the Data / Point Tolerances  / Point Tolerance Analysis option to display on the graphs the spread of the current derivative over the defined limit box.

Tolerance analysis is applied to a single point at a time, the suspension being solved for its current position, each corner and each mid point of the limit box cube, (total of 27 positions for the 3D module, but see below about mid points). Before being able to run the tolerance analysis the analysis hard point needs to be identified, (select from tree style selection box). Subsequent tolerance runs will not request for the analysis hard point as by default the previously selected point will be used. To change to a different tolerance point use the Data / Point Tolerances / Set Tolerance Point… menu and identify the new point.

{bmc bm38.bmp}
Example tolerance analysis Graphics and Graph displays

With tolerance analysis switched ‘on’ the model can be dynamically viewed and/or edited in exactly the same way as normally. Because of the increased number of solution loops the refresh time will be significantly increased. Once a tolerance point has been defined you can switch between tolerance on/off either via the menu Data / Point Tolerances  / Point Tolerance Analysis or the equivalent toolbar icon.

{bmc bm39.bmp}
Tolerance analysis toolbar Icon

Tolerance boxes when visible can be picked and dragged just like a suspension hard point. Select a tolerance box corner point with the left mouse button and drag (or joggle) it to the required position.

The mid points on each side can be optionally excluded from a points tolerance analysis. This is controlled by the Data / Point Tolerances / Solve Mid-Point menu option. When un-selected instead of 27 positions per point, this is reduced to 9 positions. The eight corners and the original position.

+$#>Overview – Graphs

The primary results display method for the application is through the derivatives graphs. Each graph show a single user selected derivative normally over the selected suspension articulation. Graph x-axis can also be set to any selected suspension result. Any number of graphs can be opened and positioned within the display using either the Graphs / New-Open menu or equivalent icon.

{bmc bm40.bmp}
New Graph toolbar Icon

In addition to plotting SDF on the graphs users can also plot Results from some of the graphical elements that have been added to the template, such as the distance between two points. These are then displayed and updated in the same way as SDF graphs. The only restriction is that Graphical element results are not involved in user lines and hence the optimizer.

The appearance and settings of each graph can be changed through either the Graphs pull down menu or the graph’s right mouse menu. By selecting a graph with the right mouse button this implies that any changes made from the menu items is applied to the selected graph only.

{bmc bm41.bmp}
Graph right mouse button menu

As each new graph is opened the y-variable is taken as the next in the available list. To change the displayed variable, use the right-mouse menu and select from the available Y-Variable list.

{bmc bm42.bmp}
Graph Y-variable list - right mouse button menu

For a model with both front and rear axles defined, two data lines will be drawn one for each suspension end. They will use different symbols, line colours and show a key to aid identification of the two results. Similarly if both left and right hand wheels are displayed on the graphical display, so both lines will be drawn on the graphs, again using different line colours to identify them.

Eight lines per wheel can be displayed on each results graph, (ignoring repeat lines with tolerance analysis). These lines being the Data Line the User Line and 5x Scope Lines. The data line is the current hard points results. The user line is an editable curve principally for visually identifying the required targets for the derivative. The scope lines are for saving incremental results to enable comparison of subsequent changes to the stored plots.

A number of menus are available to aid moving data between the Line data sets. These include;

Graphs / Copy Front/2D Data to User
Graphs / Copy Rear Data to User
Graphs / Copy Front/2D Scope to User
Graphs / Copy Rear Scope to User
Graphs / Clear Current User Line

The Scope line data is ‘grabbed’ by using the menu Graphs / Scope Line Store and is cleared by using Graphs / Clear Scope Store. Scope lines are stored in positions 1 to 5. An exclusive option is available to just store the current to position one and empty all other scope lines as well as an option to grab the current line into scope position one having first shuffled any other scope lines down one position.

{bmc bm43.bmp}
Example graph showing all three line types displayed

The deviation between the Data Line and the current Scope and User lines can be listed as a numerical sum. The displayed value is the cumulative sum of the difference for each calculated position. To display these values use Graphs / Visibility Deviation Values. The scope line used for the difference number can be changed to any of the five positions.

{bmc bm44.bmp}
Example graph showing all deviation values displayed

As a useful aid to identifying suspension characteristics, the gradient of the displayed curves can be listed both next to each individual point and for the ride condition. To turn these on use the Graphs / Visibility / Deviation Values.

{bmc bm45.bmp}
Example graph showing static gradient value highlighted

Additional Graph properties that can be defined are;

Axis Scales: Set the minimum and maximum x and y axis values. The autoscale option can also be used to automatically set the scales.

{bmc bm46.bmp}

Visibility: Set the visibility of individual graph items, Grid Lines, Deviation Values, Point Symbols, Data Values, Derivative Values, Scope Line User Line, Fit Line, Plot Title, Extended Axis Labels and Animated Cursor.

Colours: Sets the colour of individual graph items, Grid Lines, Background, Axis Lines + Text, Border Region, Data Line 2D/3D Front, Data Line 3D Rear, Scope Line 2D/3D Front, Scope Line 3D Rear and User Line.

{bmc bm47.bmp}

Line Markers: Set the marker for individual graph lines, Data Line 2D/3D Front, Data Line 3D Rear, Scope Line 2D/3D Front, Scope Line 3D Rear, User Line 2D and User Line 3D.

{bmc bm48.bmp}

Switch x-y: Switches the position of the x-y axis from the conventional x horizontal y vertical setup.

{bmc bm49.bmp}

Marker Sizes: Sets the size of the markers used for each line type, Data Marker, Scope Marker and User marker.

Text Sizes: Sets the size of the text labels for, Graph Data Values, Compliance Title, Compliance Label and compliance value.

Decimal Points Display: Defines the number of decimal points used to display numerical values. Individual values are X-Data Listing, Y-Data Listing, Derivative Data Listing, Scope Deviation, User Deviation, x-axis label, y-axis label and compliance graph.

Plot As Derivative, Plot as Integral, changes the drawn lines on the picked graph to instead of being the selected y variable, instead draws it as the derivative or integral as required.

Plot As Left and Right, Plot As Left – Right, Plot As Left + Right, changes the drawn lines on the picked graph, when showing both sides, to be either individual lines for left and right (default behavior) or Left side minus the Right side or Left side plus the Right side.

+$#>Overview – Enhanced Graphics

Enhanced graphical elements can be switched on for improved visualization of the defined model. These options have no impact on the numerical results being just aids to model viewing.

{bmc bm50.bmp}
Enhanced Graphics Menu Item

The elements affected by enhanced graphics are;

Spring, Damper, Wheel (and tyre), Pivot Axes, Grid, Body, Tubes, Tri-Facets, Triad Symbol, Origin marker, C of G marker, Moving ground and wheels and Roll Axis. An additional set of ‘enhanced graphics’ that indicate a distance measure also form part of the Enhanced graphics function. These provide distance (either in component form or resultant form) from point to point, point to line, line to line etc. Other graphics primitives such as circles, spheres, planes and cylinders also form part of the ‘enhanced graphics’ set.

For the Body element it is not sufficient to turn this ‘on’ to get the graphical body image drawn, unless a body type has already been defined either in the file or from the Data menu. To add/modify a default Body to the model use the Data / Body Type sub menu

{bmc bm51.bmp}
Enhanced Graphics body data menu

The settings for enhanced graphics visibility are stored to the users ini file.

To toggle the enhanced graphics visibility’s use the Graphics / Enhanced Visibility menus or the equivalent view toolbar icons.

{bmc bm52.bmp}
Enhanced Graphics toolbar icons highlighted

It is possible to view/edit all graphic settings through one single interface. This ‘Settings’ display can be opened via the Edit / All Settings menu item or the Ctrl +E shortcut. This provides a single control point for all graphics settings with recourse to a large number of individual pull-down menu selections.

{bmc bm53.bmp}
Graphics ‘Settings’ Display – Graphics Tab Selected

+$#>Overview – Defaults

All user definable settings are saved by the application when it has a normal program exit to its ‘ini’ file. The location of this ini file depends on the version of Windows currently being used. The file name is ‘shark.ini’ and will be saved to either C:\windows or C:\winnt. In some installations rather than being saved to the Windows folder it is stored on a by-user basis, in this instance it is stored under the Documents and Settings folder by individual login folder. This file is not directly editable by the user but there are occasions when it is useful to understand where it is and what it stores.

All colours, symbols, visibility, line types and graphics size defaults that can be set by the user are saved to this file. In addition it will retain window sizes, folder settings, and recent open files.

At application start-up this file is searched for in the relevant Windows folder and if found read in to overwrite the internal default settings.

In some extreme instances this file can become corrupt preventing the application from correctly starting. It may in this instance be thus necessary to delete this file. Deleting this file will return all defaults to the internally ‘hard coded’ values.

+$#>Overview – Data Entry

Data entry is through standard Windows style dialogue boxes. These employ standard text and numeric widgets, together with check boxes and selection boxes. Spread sheet style entry where used supports cut and paste from external applications via the clipboard.

{bmc bm54.bmp}
Example spread sheet data entry

When using ‘paste’ into a Shark spread sheet it is only necessary to select the location of the top left hand cell of the paste are that the paste is intended to fill, do not drag and highlight the entire target area.

The main data entry to the program will be of the suspension hard points x,y,z co-ordiantes. The normal route to enter this is to select File / New  and identify the required suspension end, (or both) and the required suspension template type(s). Each suspension template has default co-ordiante data associated with it to provide a easy model creation process. These default co-ordinates can be changed singularly through the on screen data edit modes of Edit, Joggle and Drag or be edited collectively through a spread sheet. The suspension data can be edited directly from the ‘File – New’ dialogue box at the point of model creation by selecting the relevant icon. Alternatively it can be accessed at any time after model creation via the relevant Data toolbar icon.

{bmc bm55.bmp}
Data toolbar icon – suspension co-ordinates display

+$#>Overview – Saving Hard Points

In the 3D module the suspension hard points can be saved either to a temporary storage for later recall during the program run, or saved to a new data file to provide a permanent record of the data input for subsequent program runs. The temporary storage facility is not available with the 2D module, the only recourse being to save the to disc as data files.

The menu item Data / Coordinates Save…option will open a text entry box to enable a unique ‘save-set’ label to be entered. This label is how the user can identify, re-load and delete it at a later stage. Coordinate sets saved in this way are only to temporary storage. Once the application is exited all coordinate save-sets are lost.

{bmc bm56.bmp}
3D Save-Set – Label Entry

Once a coordinate set has been saved it can be recalled via the relevant menu entry under Data / Coordinates / Recall Saved sub menu. Additional ‘Save-Set’ menu items are available to delete either individual save sets, (Data / Coordinates / Delete /….) or all save-sets, (Data / Coordinates / Delete All).

{bmc bm57.bmp}
3D Save-Set – Recalling a saved coordinate set

+$#>Overview – Animation

Both the 2D and 3D modules support animation of the defined models. The suspension system will be animated through a sequence of steps, appropriate to the current view mode. In the simplest mode this is over its current articulation distance, i.e. bump/rebound, roll, steer or combined. During the animation users can continue to edit and change co-ordinates, dynamically view the model or any other menu function as normally. To switch the animation on/off select the menu item View / Animation (On/Off).

{bmc bm58.bmp}
Graphics Toolbar icons - Animate Icon highlighted

When in bump/rebound displacement type the animation display is affected by the current setting for ground plane solution type, (Solve / Motion / Ground Plane). In one instance the body points are fixed and the ground plane is moved, whilst in the alternative case the ground plane is fixed and the body points are moved. This does not alter the numerical results for the suspension characteristics only the visual appearance of the animation.

{bmc bm59.bmp}
File Toolbar icons – Ground plane Icons highlighted

The animation function also applies to view modes other than displacement articulation. These include deformed geometry, modal shape and Forced-Damped response. A screen display mode tool, View / Set Display Mode Tool… allows control of these display modes.

{bmc bm60.bmp}
Setting the Screen Display Mode

An AVI file writer is also available that can be used to save an animation file. Simple options are available to automatically create the animation sequence or users can build up the animation sequence by single frame picking.

{bmc bm61.bmp}
AVI file Writer Dialogue Display

+$#>Overview – Edit Undo

After a number of changes to the suspension hard points coordinates, it is possible to step back through the changes undoing them step by step. The menu item Edit / Undo can be used for this or more conveniently the equivalent short cut key strokes Ctrl+Z. If this menu is not available then no edit events are left in the buffer to undo.

The undo buffer length can be modified from the default value, (20 steps), via the SetUp / Undo Buffer Length menu item.

{bmc bm62.bmp}
Edit undo buffer length setting

The edit undo buffer is always emptied whenever a model is loaded or saved. Thus either of these actions will lose the stored changes and hence the ability to undo any previous changes.

The undo buffer can be completely disabled if required by setting the ‘Buffer Length’ to zero. The only conceivable reason for doing this would be if it was causing an unexplained failure or it was required to run two instances of the product on the same machine, (presuming you are licensed to do so), where the undo scratch files would attempt to overwrite each other.

A by-product of the edit undo feature is that it is used to trap for machine / application failures. The temporary undo files are searched for on start-up and if found indicate a improper previous shut-down of the application. If detected the user is notified and the opportunity given to re-store the latest scratch file.

{bmc bm63.bmp}
‘Data Recovery’ dialogue box

+$#>Overview – Converting 2D to 3D

Suspension hard points in the 2D mode can be converted to full 3D data set via a program option. The user selects the 3D suspension type required and gives the additional data requirements requested, i.e. wheelbase, kingpin angle etc. Thus migration from a simple 2D concept suspension model to a full 3D suspension is a simple procedure.

Once the required 2D model has achieved the required suspension characteristics, to convert to 3D select Solve / Convert 2D to 3D. The displayed dialogue box requires the user to identify which of the valid default template types should be used, (this list will vary depending on the 2D template type used). In addition specific 3D properties need to be entered to assist in defining the properties in the third dimension.

{bmc bm64.bmp}
2D to 3D conversion data

It is not possible to add a 2D converted model as the rear axle to an existing 3D model that has a front axle already defined. The existing 3D model data will be lost.

+$#>Overview – Managing User Lines

User Lines are displayed on the graph results to visually identify the required suspension characteristics as hard point geometry is modified. Since these user lines are not considered to be part of the model, they are not saved to the data file. Thus any entered target user lines are lost whenever the application is closed.

The mechanism for the creation, saving and data-basing of user lines is the ‘Manage User Lines’ function. Managing user lines is through ‘Data Sets’, any number of data sets can be created on either the local machine or a networked server. Each data set can then contain any number of user line sets, (in this instance a ‘user line set’ refers to a user line for each possible characteristic over each possible articulation mode).

The data set references are stored in the users ini file such that on program start-up these data sets are searched for and if found added to the menu list. Once on the menu list individual user line sets can be loaded from a data set and hence used within the result graphs.

To create a new data set select Graphs / User Lines / Manage User Lines / Create New DataSet… and browse to the required file location, (creating a new folder if necessary).

{bmc bm65.bmp}
Creating a new Data Set

As part of the data set creation you will be required to define a unique label for the data set. This unique label is how the data set will be referred to when selecting sets from, sets to, or deleting from the list.

{bmc bm66.bmp}
Defining the data set label

Creating a data set will automatically add it to the ‘loaded’ data sets list. If you require to pick up a data set created by an other user, (and perhaps saved to another networked machine/server), use the Graphs / User Lines  / Manage User Lines / Include DataSet… use the browser in the conventional way to locate the required data set.

When initially created a data set will have no saved user line sets. You must subsequently add your user line sets to the required data set to make it available on subsequent re-use.

{bmc bm67.bmp}
Adding the current user lines definition to a data set.

Once a data set contains user lines these can be subsequently used by selecting Graphs  / User Lines / Manage User Lines / Load From and then select the required data set and user line set, (remember that one data set can contain many user line sets).

+$#>Overview – Compliance Solving

The standard solution technique within SHARK is for rigid body kinematic motion only. A separately licensed feature enables a linear compliant analysis to be superimposed on top of the incremental kinematic solutions. This allows users to perform modal analysis and Forced-Damped response.

To invoke the compliant solution select the Solve / 3D Compliance menu option, (note that the compliant solver is not available in the 2D module). If this menu item is ‘greyed out’ you are not licensed for this feature, (check with your software vendor or local support staff).

{bmc bm68.bmp}
File toolbar icon - Enabling the compliant solver

In its simplest form the compliant solver requires no additional data to be added to the model, (default values are assumed for tyre vertical stiffness and suspension spring rate and preload). It will treat all connection points as ‘spherical rigids’. In this form the rigids do have a stiffness value, but a high value. The default value for the rigids can be modified by the user, see Data / Compliance Data / General Data…

{bmc bm69.bmp}
Editing the default ‘Rigids’ stiffness value

With all rigid joints in the model, the only significant deflection will be caused by the flexibility of the tyre vertical stiffness. The deflection is caused by the suspension spring load. Tyre vertical stiffness values can be accessed through the Data / Compliance Data / Tyre Properties… menu (when in compliant mode) or through the equivalent ‘Graph + Data’ toolbar icon. Whilst the spring properties are accessed through the Data / Compliance Data / Spring Properties…

{bmc bm70.bmp}
Editing the compliance data spring properties

Additional graphical display features are used within the compliant solver, the visibility of which is set under the Graphics / Compliance Visibility sub menu and their properties under the Graphics / Compliance Colours and Graphics / Compliance Sizes sub menus.

{bmc bm71.bmp}
Example ‘all-rigid’ compliant model graphical display.

With the compliance model enabled additional results options are available. These include deflections and forces of the joints. Whilst deflections of the joints will be small, until we add compliant bushes, the joint forces can be used to list forces in the system due to the spring load.

All rigid joints can be edited to have compliant bush properties with three translation and three rotation stiffnesses defined. The orientation of the bushes can be aligned along any user specified local coordinate system.

Additional external forces can be applied to the model, any number of forces can be attached to individual parts under user defined magnitude and direction.

The majority of the kinematic plotting, editing and viewing functions are unchanged when using the compliant solver. The only exception involves the data editing of a suspension hard point. With the compliant solver on the data edit window is extended to include the points bush properties.

You can toggle between kinematic and compliant solver types with no loss of data. Compliant bush properties and external forces are all saved as part of the model. Note that even if a model contains compliant data when it is first loaded into the application it will appear in kinematic mode.

The Advanced analysis options for modal analysis and forced-damped response are also packaged under the compliance module, and thus you must be both licensed for and using the compliance module to be able to view these options.

+$#>Overview – Compliance Bushes

The joints in a compliant model can be either rigid, (in which case they use the default high stiffness value), or bushed. Bushed joints require the user to define three translational stiffness rates values and three rotational stiffness rates, (although some may be zero, particularly the rotational rates).

In compliant solver mode picking a suspension hard point to edit will display not only the points coordinates but also its bush properties. To switch between a ‘Ball Joint’ (rigid) and a ‘Bush’ (compliant) check the required box in the edit display. When set to ‘compliant’ the bush properties can then be edited.

{bmc bm72.bmp}
Bush Editing display – Compliant option ringed.

The bush definition requires a local coordinate system to be defined and then three translation stiffnesses and three rotational stiffnesses. The stiffnesses are defined in this local bush axis.

Bush coordinate systems have their origin at the suspensions hard point coordinates. The local z-axis is then defined as either, an absolute position, a position relative to the origin, or as another point in the model. In the case of the ‘point in the model’ this is a continuous setting such that if the reference point is moved the bush coordinate system is automatically modified.

To complete the axis definition a second point is defined that is assumed to lie in the x-z plane. The point in a plane approach is used rather than a second axis point as it is easier to identify a plane rather than an orthogonal axis. This x-z plane point can be either in absolute coordinates or relative coordinates, (note relative to the origin not relative to the z-axis point).

The defined bush coordinate system can be seen on the 3D graphics display. Both the definition points and the actual orthogonal axes are drawn, subject to separate visibility switches. To ensure both are visible use Graphics / Compliance Visibility / Bush Axis Points and Graphics / Compliance Visibility / Bush Local Axes. When these items are ‘checked’ they will be drawn on the 3D display.

{bmc bm73.bmp}
Setting the visibility options for the Bush axes.

If the bush axes definition points are visible they can be dynamically picked and edited on screen just like any hard point, (the only difference is that to avoid cluttering the display, the current ‘tracking lines’ are not drawn through them). Remember that if a z-axis point is defined as a model point then ‘dragging’ the hard point will also drag the z-axis definition point.

If using coincident points, bush axes definition points will appear on the point lists as model hard point number + 1000 or model hard point number + 2000. The +1000 point is the z-axis point whilst the +2000 point is the x-z plane point.

{bmc bm74.bmp}
3D Display - Bush axes visibility

The bush axes definition points are displayed with labels Pz and Px-z, The local axis points have labels X’, Y’ and Z’.

To enable a Forced-Damped response to be predicted in the ‘compliance’ mode, damping values for each bush need to be defined. Default values are applied in a similar manner to stiffness, the setting for which can be edited through Data / Compliance Data / General Data. Note that for a bush the damping is defined in terms of a loss angle (deg). Damping is also included for the damper(s), this is editable as a property of the damper and is defined in conventional damping terms (N.s/m).

{bmc bm75.bmp}
Damping – Editing the Damper Value

+$#>Overview – Compliance External Forces

External forces can be applied as part of the compliant model. External forces are defined in ‘sets’. The external forces can be applied either in isolation or in addition to the defined spring force. It is also possible to switch all external forces off, or individual force sets, (note you could turn both spring and external forces off and thus have no forces or compliant displacements in the model).

{bmc bm76.bmp}
Controlling the inclusion of the Spring Force

The force set intended for interactive user use is the ‘zero’ position set. By default an additional 7 further force sets are pre-filled to simulate Lotus ‘standard’ analysis load cases. The ‘standard’ sets are saved to the users ini file such that they may be modified to suit particular end users requirements. /users can add/delete user force sets as required. Each force set can contain any number of forces, each force having a defined magnitude attachment point and orientation. To edit the external force data select Data / Compliance Data / External Forces… 

The edit display shows one force set and one force in the set at a time to view the properties of other forces or sets use the two sets of arrow keys to migrate through the defined forces.

Each force is associated to a suspension corner of the model, and a part of the model for that corner. Its properties include a magnitude and a direction defined by two points. The two points define the ‘head’ and ‘tail’ of the force. Head and tail definitions can be in absolute coordinates or relative coordinates. The relative coordinates being relative to a chosen hard point, (note that added to the hard points list is the tyre contact point).

{bmc bm77.bmp}
External Force Data Edit – Add force to set highlighted

Each force set has its own ‘on/off’ setting, likewise each individual force within a force set has a separate ‘on/off’ allowing complete customisation of the defined forces.

{bmc bm78.bmp}
External Force 3D Display – Longitudinal Force to TCP

External forces are displayed on the 3D graphical display. The display shows both the definition points and the force vector. The external force visibilities are set via Graphics / Compliance Visibilities individual menu items are available the force vector and the force definition axis. External force vectors can be drawn either in fixed length form or at a scaled length, (scaled length based on magnitude). To change the fixed length size, or the magnitude scalar, edit the relevant fields in Graphics / Compliance Sizes / Edit Sizes… Note that changing the visibility setting of forces to ‘off’ does not imply that they are not used in the calculation of forces.

{bmc bm79.bmp}
Setting external force visibilities and style

If the force axis definition points are visible they can be dynamically picked and edited on screen just like any hard point, (the only difference is that to avoid cluttering the display, the current ‘tracking lines’ are not drawn through them). Remember that if an axis point is defined as relative to a model point then ‘dragging’ the hard point will also drag the axis definition point.

If using coincident points, force axes definition points will appear on the point lists as force number + 3000 or force number + 4000. The +3000 point is the head axis point whilst the +4000 point is the tail axis point.

Only one force set can be displayed on the 3D display at any one time. By default this is the zero set. The results displayed in the graphs will also be those of the currently displayed force set. Thus when changing to a different force set both the 3D display and the graphs change to reflect the new load set.

The main use of multiple load sets is to provide a set of compliance coefficients based on standard analysis cases. These can show at a glance the overall compliant response of the suspension model.

+$#>Overview – Compliance Coefficients

The compliance coefficients function is aimed at providing a single display of the overall compliant behavior of the vehicle model when subjected to a series of standard forces.

A number of external force sets are defined that together specify a series of tests. Each force set can contain a number of different forces that are applied to various parts with defined magnitude and direction. To assess the compliant response to these force sets using the ‘standard’ graphs is time consuming and not immediately visual. The compliant coefficients display provide a overall user definable summary of the compliant response.

To display the coefficients display select Results / Compliance Bar Values… The display shows for each force set, (including force set 0), a series of bar charts. The number of bars displayed on each forces sets chart depends on both the number of axles modelled and the number of variables selected.

{bmc bm80.bmp}
Compliance Coefficients display

Each bar represents the difference between the kinematic value and the compliant value of the chosen variable at the static ride condition. The compliant value can optionally include the spring force, (see right mouse menu on display).

The height of the bar is controlled by a notional scalar, each variable in each force set has its own full screen deflection scalar. To edit the scalar values select the required variables bars with right mouse button and select Edit Scale Setting. Note that the right mouse menu will appear in either ‘brief’ or ’long’ form depending if the right mouse pick is on a bar area or just on the chart.

{bmc bm81.bmp}
Compliance Coefficients ‘long’ menu form

Variables can be added to or removed from a individual load sets display using the Add Extra Variable and Remove Selected Variable right mouse menu items.

Each bar can have its own guide limit line added to its display, (by default all values are set as 0 and hence don’t appear). This is intended to provide a visual guide to the target curve without needing to read the numerical values of each bar.

{bmc bm82.bmp}
Guide Lines Added to Set 1 display

By default, force set zero is the set displayed on the 3D display and in the graphs. This is indicated on the Compliance display by the red box around its chart. To change the display’s to show one of the other force sets use the Make Force Set Default option from the right mouse menu. The red highlight will then indicate the change and the displays refreshed.

The right mouse menu also provides an easy method for turning individual force sets ‘off’, (Turn Force Set ‘Off’), gaining access to the external force data, (Open External Force Edit), make all force sets on, (Turn All Force Sets On) and toggle the inclusion of the spring force in the compliance calculations, (Include Spring force in Set).

Compliance coefficients can also be listed in textual form, Results / Compliance Text Values…. This text listing can be modified in a similar way to the original bar chart display by positioning the cursor at the relevant point in the text, (ensure you actually select the position), and using the right mouse button to pull up the appropriate menu options. This gives access to the same functionality as the bar charts.

{bmc bm83.bmp}
Example Compliance Coefficients Text Listing

+$#>Overview – Deformed Geometry Animation

As with the kinematic solution the compliant model can be animated over the currently specified articulation. The additional feature of animating the displacements of the compliant model is the inclusion to the display of the calculated forces. To set the visibility of the calculated forces set Graphics / Compliance Visibility / Calculated Forces.

The additional animation type that can be applied to a compliant model is that of the deformed geometry. This is similar in concept to the ‘mode shape’ animation used in Finite Element packages. 

{bmc bm84.bmp}
Example Deformed Geometry Plot

Deformed geometry animation, cycles through a series of display steps between the kinematic solutions positions and the compliant position. This animation is performed for a specific articulation position, (normally the ride position), although the user can select which animation position to animate at, (View / Set Display Mode Tool). Where 0 is the ride position 1 is the first bump/roll or steer position, (as appropriate). If the position number entered is greater than the number of increments it will be clipped to the maximum.

Because the deformations can be small animating in steps between kinematic and compliant may need scaling to enhance visualization. The deformed geometry scalar can be set by View / Set Display Mode Tool. The setting of this will distort all displayed 3D compliant images, so should be set back to 1.0 when not required.

{bmc bm85.bmp}
Setting the deformed geometry scalar

Deformed geometry animation can be turned ‘on’ with one of two options, View / Animation (On/Off), with Screen Display Mode set to Deformed Geometry. The two options are with or without spring forces. Whilst both options function in the same way the second option will illustrate the bush deflection due to the applied external forces only and not the combination of external forces and spring force. The ‘Set Display Mode’ tool allows a convenient single point to control animation and display modes, View / Set Display Mode Tool.

{bmc bm86.bmp}
Specifying Deformed Geometry Display via the ‘display mode’ tool.

+$#>Overview – Hard Point Joggle

The suspension hard points can be selected from the screen via the mouse and ‘joggled’ to a new position, the suspension derivatives being re-calculated as the hard point is moved. The selected derivatives that are being displayed graphically are updated during the hard point screen joggling. Point joggling can be in a 2D view along both viewed axes, a single axis or joggling in a 3D view along a selected axis direction.

{bmc bm21.bmp}
Graphics Screen – Joggling mode, tracking lines show Y axis direction.

The majority of the point joggling functionality is performed using a combination of left and right mouse buttons. The mouse buttons are also used extensively for the dynamic viewing option and thus this ‘sharing’ requires a switch between ‘edit’ mode and ‘dynamic view’ mode.

Point joggling is one part of the ‘Edit’ mode. The other two parts are direct editing and point dragging.

To indicate when the application is in ‘dynamic view’ mode and when in ‘Edit’ mode not only are the relevant menus and icons ‘checked’ but also ‘corners’ are added to the graphic display when in ‘dynamic view’ mode.

{bmc bm18.bmp}
Graphics Screen – Indicating in Dynamic View mode.

To change to editing mode un-select ‘dynamic viewing’ using View / Dynamic Viewing / Off. Alteratively select the dynamic viewing icon from the ‘view’ toolbar.

{bmc bm19.bmp}
Dynamic Viewing Icon- Shown as ‘on’.

When in point joggling mode ‘tracking lines’ are drawn to indicate the current ‘tracking’ direction(s). To change the current tracking direction the right mouse button will cycle through the available tracking direction options. A similar action is achieved by selecting the mouse icon from the ‘view’ toolbar.

{bmc bm20.bmp}
Mouse Icon – Cycles through tracking options.

Selecting any of the ‘Edit icons’ changes the mode to edit and cancels the dynamic view mode. In a similar way selecting any of the three dynamic view icons changes to ‘dynamic view’ mode.

The joggle symbol indicates the number of tracking directions available and also which of the four arrow keys, (left, right, up and down), is likely to be used. To use joggle select either Ctrl + Arrow Key for coarse joggle or Shift + Arrow Key for fine joggle. The joggle fine size is a tenth of the coarse size, the coarse size can be set via SetUp / Gen Defaults…

{bmc bm87.bmp}
Setting the default Coarse Joggle Step Size

Point joggling is affected by both Groups and Coincident points. The settings for groups and point coincidence change a single point pick and joggle event into a potential single point pick but multiple point joggle, (using a temporary group). In the case of groups, the current groups points are all translated by the same amount. Whilst for point coincidence only the point or points selected from a displayed list are moved, again all selected points are moved by the same amount.

{bmc bm22.bmp}
Example Coincident point pick

The coincident point selection feature is switched on via the Edit / Point Coincidence Pick menu. When switched off the nearest point to the picked position is always selected. The tolerance used to decide whether two points are coincident, can be changed via the SetUp / Gen Defaults… menu. A similar tolerance exists to control whether a point is within the pick region.

+$#>Overview – Point Coincidence

The Point Coincidence function controls the modification of hard point coordinates. When enabled selecting a point that is in close proximity to another the user is prompted to identify, which of the points within the coincidence tolerance is to be edited. To enable point coincidence select Edit / Point Coincidence.

{bmc bm88.bmp}
Enabling point coincidence

Coincidence tolerance defines the radius in the view plane from the picked point that is used to check for coincident points. If coincident points are found a menu is displayed listing the points found. You can then either select one of the identified points or ‘All Points’. Selecting ‘all points’ is equivalent creating a temporary group, all points are then moved by the same amount, (note that this does not make them coincident).

{bmc bm22.bmp}
Example Coincident point pick

When the coincident point function is switched off the nearest point to the picked position is always selected. The tolerance used to decide whether two points are coincident, can be changed via the SetUp / Gen Defaults… menu.

{bmc bm89.bmp}
Setting the Coincident point tolerance

+$#>Overview – Data File Text Editor

The Data file text editor is a dialogue box that can be used to view and edit data files in a purely textual environment. This is an advanced user feature only that is primarily intended for debugging use and is not recommended as a normal working practice. This is primarily because the data file format is not formally declared.

To load a saved data file into it use the local menu File / Open alternatively to load the current model into the display select from the local menu File / Load Current.

Any edited changes can either be saved to a file , File / Save  or File / Save As or the current model can be updated with the contents of the text display using File / Make Current.

Note that the current model and the data text display are only synchronized when a Load Current or Make Current command has just been made. Once a data change in either has been made they will only then be synchronized when the change is ‘made current’ to the other.

{bmc bm90.bmp}
Screen Shot – Text Data File Editor

+$#>Overview – Hard Point Editing

Hard point editing is the simplest method of editing single suspension hard points values. In the 3D module complete display and editing of the hard points can be carried out via the alternative spread sheet display.

The mouse buttons are used extensively for both editing and the dynamic viewing option and thus this ‘sharing’ requires a switch between ‘edit’ mode and ‘dynamic view’ mode.

Direct editing is one part of the ‘Edit’ mode. The other two parts are point dragging and joggle editing.

To indicate when the application is in ‘dynamic view’ mode and when in ‘Edit’ mode not only are the relevant menus and icons ‘checked’ but also ‘corners’ are added to the graphic display when in ‘dynamic view’ mode.

{bmc bm18.bmp}
Graphics Screen – Indicating in Dynamic View mode.

To change to editing mode un-select ‘dynamic viewing’ using View / Dynamic Viewing / Off. Alteratively select the dynamic viewing icon from the ‘view’ toolbar.

{bmc bm19.bmp}
Dynamic Viewing Icon- Shown as ‘on’.

When in edit mode ‘tracking lines’ are drawn to indicate the current ‘tracking’ direction(s). This is not relevant to the hard point-editing mode as tracking only applies to the dragging and joggle edit modes.

Selecting any of the ‘Edit icons’ changes the mode to edit and cancels the dynamic view mode. In a similar way selecting any of the three dynamic view icons changes to ‘dynamic view’ mode.

When in direct editing mode to edit a point select it with the left mouse button on the graphics display. The displayed dialogue box will be different if in the 2D module or the 3D module.

{bmc bm91.bmp}
2D Direct Data Editing

3D data editing lists the selected hard points x, y and z co-ordinate. To change simply edit and select ‘Ok’. Note that the cancel button or the ‘Esc’ key will close the edit box and ignore any changes. To subsequently undo a change, use the undo function.

{bmc bm92.bmp}
3D Direct Data Editing

For the 3D module, in addition to the points x, y and z co-ordinates, other properties are also displayed that can be edited. These include;

Point Long Label, the long-label used in graphics, menus and listings to identify this point. Maximum of 80 characters long.

Point Short Label. the alternative short-label or point No. used to identify this point. Can be numeric or textual up to a maximum of 8 characters.

Co-ordinate, note that the co-ordinates may be either global or local values, depending on the definition co-ordinates system. If local values they will have the string “(local)” on their description.

Definition Coordinate System, identifies if the point is in the default global co-ordinate system or one of the optional user defined local axis systems.

Optionally visible variables

Part 1 for Point, identifies the first part that the point is associated with. A point must be associated with at least one part and a maximum of two parts. (a point associated with two parts indicates the connection point between these two parts, i.e. a joint. Normally the association of points to parts is made directly by the template definition or by graphics picking when the point is created.

Part 2 for Point, identifies the second part that the point is associated with. A point must be associated with at least one part and a maximum of two parts. (a point associated with two parts indicates the connection point between these two parts, i.e. a joint. Normally the association of points to parts is made directly by the template definition or by graphics picking when the point is created. For a point associated with only one part this option would be set to ‘None’.

+$#>Overview – Import and Export to Adams Sub Systems

A utility routine is provided that enables suspension hard point coordinates to be transferred to and from an Adams sub-system model. This transfer is facilitated by the use of a supplementary text string that can be assigned to each hard point within Lotus Suspension Analysis (LSA). This text string is the label that is used within the Adams sub-system (and thus relies on consistent naming within your Adams sub-systems). The routine works on one end at a time since an Adams sub-system model would normally only have a single suspension corner modeled. Thus if the LSA model is a full vehicle, the user needs to identify which LSA end is to be used. See local menu setting under ‘Data / Import to Front’ or ‘Data /Import to Rear’. The same setting is assumed on Export only the local menu text changes.

{bmc bm93.bmp}
The Import/Export Display , Shown for Import, ‘scale’, ‘shift’ and ‘switch’ items highlighted.

The import and export routine also has the option to shift the values, scale the values and switch the axis order. On import the ‘shift’ is added to the value in the Adams sub-system, whilst on export the ‘shift’ is subtracted from the LSA value. A shift value can be defined independently for x, y and z. A similar editing display is provided for the ‘scale’ settings, the default values for which are 1.0.

{bmc bm94.bmp}
Editing The ‘Shift’ values for Import and Export.

The axis switch settings are set through a selection display. The default setting is for direct association of equivalent axes, i.e. x with x etc. This can be changed should a switch be required.

{bmc bm95.bmp}
Editing The ‘Switch’ settings for Import and Export.

The individual point text strings are stored as part of the template descriptions. Thus they can either be edited through the normal template editor dialogue display on the ‘points’ tab or they can be edited from within the Import/Export window via the Data / Edit Point Label Strings menu option. In both case these settings would need to be saved either with the data file, (by enabling template save to the data file, see settings menu options) or by saving the modified template as a user defined or custom template. Each point can have three associated text strings, the first is for the point position whilst two others are provided to identify local bush axis positions. All text fields are optional and can be set to ‘Not Defined’ if not required or unknown. A special text description ‘DERIVED’ is used for some points such as the stub axle point and the strut lower slider axis point. These are not extracted directly from the sub system file but are calculated either in the case of the strut point from the other points or as in the case of the stub axle point, from additional extracted data values. The point strings can also be math’s functions such as [(P1+P2)/2.0]. The use of a math’s function is indicated by the use of square brackets [ ] to bound the string. This indicates that the point string should be treated as a math’s string with reference to other points via their position in the template i.e. P4 is the fourth point in the template. As points are processed in order it is possible to use this sequence to use a math’s function to define point 5 and then reference point 5 in a latter points definition, say point 8. Note that the point number is position in the template and not the local ‘point number’ as defined in column 1 of the ‘settings’ tab of the template editor. The math’s function reader is loosely based around Fortran syntax. Key intrinsic functions recognized include, SQRT, SIN, COS, TAN, SIND, COSD, TAND, ASIN, ATAN, ACOS, ASIND, ACOSD, ATAND, LOG10, SINH, COSH, TANH, LOG, EXP AND ABS. The standard symbols +, -, * (for multiply), /, **(for power) are used whilst simple round ( ) brackets can be used within the string to force computation sequence.

{bmc bm96.bmp}
Editing the Text ‘Strings’ through the Template Editor.

From within the Import display three menu items are provided to access the three text fields, Data / Edit Point Label Strings, Data / Edit Bush Z-axis Label Strings and Data / Edit Bush X-Z Plane Label Strings. These provide a local means of editing the template settings. 

{bmc bm97.bmp}
Editing the point label strings from the import display.

Additional strings are used to identify supplementary model data. They also provide a means by which ‘left’ and ‘right’ is identified since this may be subject to local language issues. The Data / Edit General Label Strings menu item displays these current settings. Because they are considered local user settings rather than model specific they are saved as part of the users ini file. 

{bmc bm98.bmp}
Changing the ‘General’ Settings Strings.

To import hard points from a sub model first ensure that the relevant point strings and general strings are correct for the current template. Open the import display and use the File / Open (sub system) to locate and load the required sub system model. The data extraction can be previewed in the lower display section using the File / Import Hard Points (Preview) menu option.

{bmc bm99.bmp}
Example Hard Point Import, template type 1.

To populate the current LSA model with the values extracted from the sub-system use the File / Import Hard Points. If settings have been changed from the default for the ‘shift’, ‘scale’ and ‘switch’ they are applied in the order ‘Shift’ then ‘Scale’ and then ‘Switched’.

The Export function works in the same manner as Import but the order of shift, scale and switch is reversed. 

+$#>Overview – Adding a Hard Point to a Model

The number of hard points in a model is controlled by the appropriate template. Points can be added by modifying the template using the standard template editor, see File / Edit Templates menu item. Additional points can be added to a model directly through the graphical viewer via the Edit / Add to Model / Add Point menu items. These added points would not normally be used to modify the overall connectivity but more likely be used to add additional user graphics.

{bmc bm100.bmp}
Adding a Hard Point to the existing model, add options highlighted.

Points can be added through the menu either to ground (i.e. the body) or to any picked part. When adding to the body the user must provide the new position in global coordinates. A point added to an existing part can be added in absolute coordinates, relative to a point or between two points. When adding points to a part, once the part is picked the display will switch to just show that part and its associated points in a similar manner to the free body display. When in ‘Part’ pick mode, the part labels are made visible and the part ‘centre’ points drawn.

{bmc bm101.bmp}
Adding a Hard Point via the template editor, .

+$#>Overview – Adding Graphics to a Model

Graphical elements are stored as part of the template structure and control the visual appearance of a model. The user can add additional graphics elements by direct editing of the template through the standard template editor, see File / Edit Templates menu item. Additional graphical elements can be added to a model directly through the graphical viewer via a series of menu items under the Graphics / Add Graphic and Graphics / Add Measure sub-menus.

{bmc bm102.bmp}
Adding a Graphical Element to the existing model, add options highlighted.

Each added element is appended to the current template list, thus by adding graphics from the menu the user is modifying the template. To retain these changes users need to ensure they save the modified template either by inclusion into the data file, or by saving the template to a custom or user template file. 

Graphical elements can be picked on screen and deleted if required. Again this will remove them from the current template and permanent changes would need to be saved as indicated above.

The list of available graphical elements is broken down into seven sub sections listed below;

	Line
	Cylinder
	Circle
	Sphere
	Facet
	Plane
	Components

The list of available measure elements is broken down into two sub sections listed below;

	Distance
	Angle

Each sub section has a number of specific ways of defining the associated primitive.

	Lines:
Pnt-Pnt Line: Adds a new Line graphical element to the selected ends’ template. Two hard point picks are required, points need not be on the same part.
Pnt-Vector Line: Adds a new Line graphical element to the selected ends’ template. Three hard point picks are required, a line is drawn through the first point who’s direction is set by the vector defined by the second and third picks, points need not be on the same part. The first and second picks can be the same point. The line is drawn to a global clipped length.
Pnt-Xvector Line: Adds a new Line graphical element to the selected ends’ template. One hard point pick is required, a line is drawn through the picked point in the global X axis direction. The line is drawn to a global clipped length.
Pnt-Yvector Line: Adds a new Line graphical element to the selected ends’ template. One hard point pick is required, a line is drawn through the picked point in the global Y axis direction. The line is drawn to a global clipped length.
Pnt-Zvector Line: Adds a new Line graphical element to the selected ends’ template. One hard point pick is required, a line is drawn through the picked point in the global Z axis direction. The line is drawn to a global clipped length.
		Pnt-Plane-Norm: Adds a new Line graphical element to the selected ends’ template. A line is drawn through the selected point in a direction normal to the selected plane. The plane is identified by three point picks. The line is drawn to a global clipped length.
		Pnt-UserVector: Adds a new Line graphical element to the selected ends’ template. A line is drawn through the selected point in a direction defined by a user vector. The line is drawn to a global clipped length.
		Pnt-Vector^Vector Line: Adds a new Line graphical element to the selected ends’ template. A line is drawn through the selected point in a direction defined by the cross product of two user defined vectors. The line is drawn to a global clipped length.

	Cylinders:
Pivot: Adds a new Pivot graphical element to the selected ends’ template. Two hard point picks are required, both points need not be on the same part.
Tube: Adds a new Tube graphical element to the selected ends’ template. Two hard point picks are required, both points need not be on the same part.
Vector-Radius-Length: Adds a new cylinder graphical element to the selected ends’ template. Drawn through the selected point in a direction defined by the second and third point picks. The radius and length of the cylinder are defined directly.

	Circles:
Pnt-Pnt-Pnt: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required through which is drawn a circle, both the circle centre and radius are calculated and displayed as part of the graphical display.
Cntr-Rad-Norm: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required. The circle is drawn centered at the first point of a defined radius and who’s normal is defined by the second and third picks. The first and second picks can be the same point.
Cntr-Pnt-Plane: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required. The circle is drawn centered at the first point and is drawn through the second point, (i.e. defines the radius), in a plane that contains the third picked point. All picked points must be different.
Pnt-Normal: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required. The circle is drawn through the first point about the defined normal vector. All picked points must be different. The derived circle centre and radius is drawn as part of the graphical element display.

	Spheres:
Pnt-Pnt Radius: Adds a new Sphere graphical element to the selected ends’ template. Two unique hard point picks are required. The sphere is centered at the first pick and the radius is set by the second pick.
Pnt Radius: Adds a new Sphere graphical element to the selected ends’ template. One hard point pick is required. The sphere is centered at the pick and given the radius specified by the user.
Pnt-Pnt Dia: Adds a new Sphere graphical element to the selected ends’ template. Two unique hard point picks are required. The sphere is centered at the mid point of the two picks, the radius being half the distance between them.
Pnt-Pnt-Pnt-Pnt: Adds a new Sphere graphical element to the selected ends’ template. Four unique hard point picks are required. The sphere is drawn through the selected four points. Four points will define a unique sphere who’s calculated radius and centre position is identified as part of the drawn graphical element.

	Facets:
Pnt-Pnt-Pnt Facet: Adds a new Triangular Facet graphical element to the selected ends’ template. Three hard point picks are required, points need not be on the same part.
Pnt-Pnt-Pnt-Pnt Facet: Adds a new Four noded Facet graphical element to the selected ends’ template. Four unique hard point picks are required, points need not be on the same part. Whilst points need not be in a plane, any facet drawn of non-planar nodes is not fully defined.

	Planes:
Pnt-Pnt-Pnt Plane: Adds a plane graphical element to the selected ends’ template. Three unique hard point picks are required, points need not be on the same part. All plane elements are drawn clipped to a global value, (which the user can edit).
Pnt-X-Y Plane: Adds an X-Y plane graphical element to the selected ends’ template drawn through the selected pick. All plane elements are drawn clipped to a global value, (which the user can edit).
Pnt-X-Z Plane: Adds an X-Z plane graphical element to the selected ends’ template drawn through the selected pick. All plane elements are drawn clipped to a global value, (which the user can edit).
Pnt-Y-Z Plane: Adds an Y-Z plane graphical element to the selected ends’ template drawn through the selected pick. All plane elements are drawn clipped to a global value, (which the user can edit).
Pnt-UserVector Plane: Adds an plane graphical element to the selected ends’ template drawn through the selected pick. The orientation of the plane is controlled by two user defined vectors. All plane elements are drawn clipped to a global value, (which the user can edit).

	Distance
Pnt-Pnt Dist: Adds a point to point distance graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The display shows the total distance between the two points.
Pnt-Line Dist: Adds a point to line distance graphical element to the selected ends’ template. Any three hard point picks are required, all points must be on the same suspension corner. The last two picks define the required line. The display shows the total perpendicular distance between the point and the line.
Line-Line Dist: Adds a minimum distance between two lines graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first two picks define one line whilst the last two picks define the other required line. The display shows the minimum normal distance between the two lines as a total distance.
Pnt-Plane Dist: Adds a points’ distance from a plane as a graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first point is the required point whilst the last three picks define the required plane. The display shows the normal distance between the point and the plane as a total distance.

	Components
Pnt-Pnt Comps: Adds a point to point distance graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The display shows the distance between the two points in its x, y and z components. 
Pnt-Line Comps: Adds a point to line distance graphical element to the selected ends’ template. Any three hard point picks are required, all points must be on the same suspension corner. The last two picks define the required line. The display shows the perpendicular distance between the point and the line in its x, y and z components. 
Line-Line Comps: Adds a minimum distance between two lines graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first two picks define one line whilst the last two picks define the other required line. The display shows the minimum normal distance between the two lines in its x, y and z components.
Pnt-Plane Comps: Adds a points’ distance from a plane as a graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first point is the required point whilst the last three picks define the required plane. The display shows the normal distance between the point and the plane in its x, y and z components.

	Angles:
Pnt-Pnt-Pnt Angle: Adds an angle between three points graphical element to the selected ends’ template. Any three hard point picks are required, all points must be on the same suspension corner. The middle picks is the point for which the angle is given. The display shows the angle created by the three point picks in degrees. 
Pnt-Pnt Z-Axis Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global Z-axis vector. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt Z-Axis X-X component Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global Z-axis vector but only the component around the X-X axis. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt Z-Axis Y-Y component Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global Z-axis vector but only the component around the Y-Y axis. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt X-Axis Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global X-axis vector. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt X-Axis Z-Z component Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global X-axis vector but only the component around the Z-Z axis. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt X-Axis Y-Y component Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global X-axis vector but only the component around the Y-Y axis. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt Y-Axis Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global Y-axis vector. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt Y-Axis Z-Z component Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the global axis vector. The display shows the angle created by the two point picks in degrees.
Pnt-Pnt Y-Axis X-X component Angle: Adds an angle between a vector and an axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The two picks define a vector, (the first point being the start of the vector) and the angle is relative to the appropriate global axis vector. The display shows the angle created by the two point picks in degrees.

Individual graphical element types have their own specific data requirements some are unique to each element and others are relevant to each class of element. These settings and values can be edited by picking the relevant element. Hint, hover over the approximate centre of an element and check the status bar prompt to confirm required element will be selected.

{bmc bm103.bmp}
A ‘Pnt-Plane Dist’ Graphical Element added to a type 1 model.

+$#>Overview – Free Body Graphical Display

The free body display mode can be switched on via the View / Free Body Diagram… pull down menu. When enabled the display changes to show only the selected part and it’s associated points, graphical elements and forces. In this mode the interface functions exactly as normal, i.e. dynamically viewed, animated, edited etc but only that parts elements are involved. A small selection box is used to control the free body mode enabling the user to select the required corner and part.

{bmc bm104.bmp}
Setting the Part for Free Body Display.

The free body mode can be cancelled either by un-checking the menu item that was used to enable it, or by closing the free body selection box.

{bmc bm105.bmp}
Example free body display for a lower wishbone in compliant mode.

+$#>Overview – Kinematic Sum Display

The kinematic sum display is a means by which the weighted sum of the deviations of selected results when compared to a target value can be displayed. This single value allows a simple metric to be used to compare a change in a particular suspension property effect over a whole range of results.

{bmc bm106.bmp}
Kinematic Sum Display.

Results that can be included into the ‘sum’ include all graphs results, (visible or otherwise), and all compliance bar graphs. Individual weighting factors can be applied to each selected result. A number of convenience functions are provided to automatically set these weighting values mostly based around the current display axes settings. 

The sum value is the cumulative of all individual deviations from target. In the case of the compliance coefficients these targets are set by selecting each bar chart in turn and defining the required value. In the case of the characteristic graphs, (i.e. toe, camber castor etc.), the target line is the user line set for each graph. The deviation is then the difference between either the single target value (for the compliance coefficients) or the average of the differences of the actual curve from the defined line for a characteristic graph.

{bmc bm107.bmp}
Example Characteristic Graph, showing its contribution to the sum.

The importance of the ‘Kinematic Sum’ is that since it can be used by the user to view the impact of a single change on a set of potential compromise results, it can also be used by an optimization routine as indicating the direction of change for achieving an optimum design. This optimization potential is covered in the next section.

+$#>Overview – The Internal Optimizer

The kinematic sum is used to apply a sensitivity-based optimization to the model. Parameters are defined that have a start value, range and increment. Parameters can be point position, bush stiffness and bush orientation. The Kinematic sum as discussed previously can optionally include any characteristics graph or compliance coefficient.

{bmc bm108.bmp}
Expanded Optimizer Display, View / Details option checked.

The settings for the optimization are editable through a single display. With sections for defining which results to include, weightings to apply and settings for parameters.

{bmc bm109.bmp}
Optimizer Parameter Summary.

Parameters are applied in reverse sensitivity order, the most sensitive applied last. A sensitivity threshold value is applied such that parameters that do not significantly affect the sum can be automatically screened. As the optimization is proceeding the graphical display is updated and a rolling display shows the changes to the ‘sum’.

{bmc bm110.bmp}
Optimizer Rolling Sum Display.

Once the optimizer run has finished the user is asked to confirm acceptance of the changes. Selecting ‘no’ will return the model to the pre-run condition. User can stop a run early either through manual interjection or through a software defined minimum target value.

+$#>Overview – Display Units

The units used in the display of both the data and the results can be changed from the default settings of Angle - deg, Length – mm, Mass - kg and Force - N to other available options. The options are given below for each variable type. A user defined ‘unit’ option is also available for each parameter.

	Angle:	Radian
		MilliRadian
		Degree (default)
		Minutes
		User-Defined

	Length:	Meter
		milliMeter (default)
		User-Defined

	Mass:	Kilogram (default)
		User-Defined

	Force:	Newton (default)
		decaNewton
		User-Defined

It must be remembered that this is a ‘viewing’ option only and data files will always be saved using the original ‘default’ unit settings. This also applies to the text editor within the program since this is merely an editor of ‘saved’ data files.

The units can be set either from the ‘New Model display’ or directly from the menu items SetUp / Change Units. 

{bmc bm111.bmp}
Opening the units Tool from the ‘New model’ display.

The settings for each unit includes a scale factor, the number of decimal points (to add or remove compared to the default settings) and the label.

{bmc bm112.bmp}
Changing the units display.

These view unit settings are saved as part of the users configuration ‘ini’ file and are not saved with the data file. Whilst the units can be changed at any time, it should not be carried out when you have a data display window open as this could lead to incorrect data unit conversions. 

+$#>Overview – Modal Analysis

Modal analysis can be applied to any compliant model. To correctly predict modal frequencies and shapes the part masses and bush stiffness’ must be defined. The modal analysis calculates as many natural frequencies as there are degrees of freedom in the model. Frequencies are sorted into ascending order and the user can select an individual mode to view/animate. Mode shapes can be selected and animated via the View / Set Display Mode Tool.

{bmc bm113.bmp}
Setting the display mode to Mode Shape – 8th mode Selected.

The required mode shape can either be set via the selection box to the right of ‘mode shape’ toggle or through the ‘Modal Frequencies’ results plot. To display the Modal Frequencies results plot select Results / Modal Analysis Display.

{bmc bm114.bmp}
Modal Frequencies Screen Shot – 8th mode Selected.

The selected modal shape is also shown drawn or animated in the main 3d view with an associated scalar. This allows the user to view each mode shape in turn.

{bmc bm115.bmp}
Modal Frequencies Main View – 5th mode Selected.

+$#>Overview – Forced-Damped Analysis

The Forced damped analysis takes a compliant modal and calculates the amplitudes of all points in the model over a specified frequency range under the current force set. Defining the required force set is important as this controls which natural modes will be excited. The force can optionally include the spring force(s). Damping is added to the model for both the damper elements and the bushes. Bush damping is defined by a loss angle setting whilst the damper elements have their damping directly defined.

{bmc bm116.bmp}
Changing the View to Forced Damped – 15.4 Hz selected

The forced-damped display can be for any specified frequency. This can be set either via the slider in the ‘set display mode’ dialogue box or directly in the value entry. In addition the response of the system through a complete frequency sweep can be displayed, Results / Forced-Damped Speed Sweep Display. The displayed graph can be control to set the required range and amplitude scales. Because this speed sweep is relatively time consuming to perform, (in Shark terms at least), this speed sweep display is only updated when first opened or when the ‘refresh’ option is selected.

{bmc bm117.bmp}
Forced-Damped Speed Sweep Display – 15.4 Hz point shown

As with the modal analysis the forced-damped response for the current frequency can be viewed/animated in the main window with a defined scaler.

+$#>Overview – Creating a Full Axle Model

The simplest type of template is for an independent suspension based on a single corner, (one wheel). For some suspension types such as rigid axles you will always need to model both wheels in the initial template. Whilst with independent suspensions you have the option to make them single wheel or double wheel template. If it is required to analyze the impact of suspension parts that connect both corners together such as steering rack, anti-roll bar and sub-frames then a full axle model would be required.

To convert a corner template to a full axle you can either edit the template directly through the template editor, File / Edit Templates or use the convenience data menu options. If you edit the template directly you will need to duplicate all the existing points changing the default Y co-ordinate to be the mirror of its partner, tag the specific points such as upper ball joint(2) and set the point symmetry options. Far simpler is to use the convenience function Edit / Convert Corner to Axle Model which completes all this for you.

{bmc bm118.bmp}
Default Template 1 converted to full axle model

Once converted to a full axle template you can now add features such as the compliant rack and anti-roll bar. Further convenience functions are available to simplify these tasks. The compliant rack add menu Edit / Add to Model / Two Part Rack to Model option requires the user to identify which part the roll-bar drop link should be attached to. Once selected the user is prompted for a point position and then all necessary modifications are made to the template. It should be remembered that this template modification needs to be saved, either as a custom template, user template or saved with the data file (Setup / Include User Templates In Data Files).

{bmc bm119.bmp}
Anti-roll Bar Added to Full axle version of Default Template 1.

To add a compliant rack to the template use Edit / Add to Model / Two Part Rack, this just requires both the left and right steering attachment points have been tagged in the template so that the rack can be correctly included into the model.

+$#>Overview – User Defined Custom Controls

Users who wish to build their own custom displays can do so through the Window / Open New Custom Control Display menu option. Dialogue boxes created in this way can be distributed to other users as saved specification files. Individual user settings are saved as part of the ini file such that they are available for repeat use.

{bmc bm120.bmp}
Example custom template dialogue box- showing data sliders

These custom displays are completely editable not only in terms of widget content but also the associated commands, data values and results. Thus a custom display can be used to group a set of specific data variables together into a single window with some specific menu commands. Alternatively they may provide a collection of results graphs for standard results viewing.

{bmc bm121.bmp}
Example custom template dialogue box - showing data and results options

To create your own custom display, select the Window / Open New Custom control Display menu option. This will display a new empty display, (save for simple text widgets). To change the display, select the 'Edit' option. You can modify, add and delete widgets from the display.

{bmc bm122.bmp}
New display in 'edit' mode

To delete an existing widget(s) select the widget with the mouse and 'delete'. The right mouse menu has a number of functions that allow you to align widgets to improve appearance.

Widget types that can be added include, Buttons, Toggles, Sliders, Text Display/Entries, Value Display/Entries, Icon Buttons, Gauges, SDF Graphs, Bar charts and Bars. Each has a set of properties that can be edited via the 'Properties' option. The properties specific to the dialogue box can be edited through the right mouse menu.

{bmc bm123.bmp}
Properties display for dialogue box

Users can save the settings for a particular display such that it can be shared with other users. Custom control settings are automatically include in a users ini file for future use. To save it for use by other users, in 'Edit' mode select the save option and define the required file name and location. Users can then use the 'load' option to use this file to create their own copy of it. A custom control display is not lost by simply closing the display, its settings are saved and is available from the list of displays at any time in the future. To permanently remove a custom display from the list you must use the 'WinDelete' option whilst in 'Edit' mode.

+$#>Overview – Auto-Search and Load

The Auto-search and load facility provides a semi-automatic means by which the current models hard point positions can be modified by an external application during a live Shark session. This facility uses an intermediary shared text file, Shark checks the status of this file at a pre-defined time interval to check for changes. If the file has been modified since last read then its contents are checked and any identified co-ordinates extracted.

{bmc bm124.bmp}
Activating the Auto Search and Load facility

This facility can be run in one of three modes. The first is a single Scan, ‘Scan Once’. On selection it will scan for the defined file and attempt to identify and extract hard point data irrespective of the files last modification status. The second is a repeated scan but with a prompt and confirmation from the user before any updating is applied. The third is a fully automatic repeated scan that will apply any changes it identifies without requesting user authorization or announcing a change.

{bmc bm125.bmp}
Auto-load prompt for option 2 new points found

The repeated scans, (options 2 and 3) are performed at a prescribed interrupt time interval. The default value for this is 3000 mSecs but the use can edit this through the ‘Edit Timer’ menu item.

{bmc bm126.bmp}
Editing the interrupt time

No restrictions are placed on the position of intermediate text file, thus it could be on the local disc or even a shared network drive. The menu option ‘Edit File Name’ provides a simple file dialogue box with browser to define/locate the shared ASCII text file.

{bmc bm127.bmp}
Editing the shared file name and location

The format currently used in the shared file is one based on simple ASCII text. Each line contains a record that is read as a string and then that string checked for a match against the point labels used in the current models template(s). If a ‘full’ match is found, (note partial matches are ignored), then the string is re-read to identify the number of values on the line. They are assumed to be global co-ordinates in the order of X, Y and then Z.. It is not necessary to have all three values present but the X, Y, Z order is always applied. As well as looking for a match with the template ‘point labels’ the ‘Adams Point import label’ is also checked for a match.

{bmc bm128.bmp}
Matching Labels with the Current model Template

An example of what the shared file may look like is given below for a simple two-point example. Note that the first record is a simple version flag, (currently set as 1). This is to allow for future expansion with potential expansion into user specific formats and greater data options, (i.e. bush properties, graphics etc.).

{bmc bm129.bmp}
Sample shared file format

To stop the repeating auto-search and load options either select the cancel option when the relevant prompt is displayed or use the ‘Off’ menu option.

+$#>Overview – Component-Setup Toolbox

The Component toolbox is a utility that allows the user to create a library of “standard” alternatives for each part in the current models template(s). Each part in the toolbox has a characteristic length and the alternatives have different length properties. The parts that can appear in the toolbox are Wishbones, Tie Rods and Spacers, (currently uprights with their potential for up to six defining lengths are not included). The toolbox can thus be used to investigate the effect on suspension derivatives when mixing these alternative standard components.

{bmc bm130.bmp}
Initial Opened empty Toolbox – Select to Add Parts

To open the toolbox utility select the appropriate menu from the ‘data’ pull down menu. On initial opening it will be empty. You can add as many or as few of the current parts to the toolbox. To add parts to the toolbox select on the top horizontal panel with the left mouse. Here you can select individual parts from a list or use the ‘Auto-load all Parts and Spacers’ option to load all valid parts.

This is initial add will place the part in the toolbox and add one ‘alternative’ for each added part, this alternative being the baseline as extracted from the current model. If you select on the parts top header box menu options are given to Remove the part from the toolbox (and any alternative options of it), Edit the label used for the part, add an option to the part or Auto-create a range of alternative options for this part.

{bmc bm131.bmp}
Parts Added – Alternative options menu shown

Along the bottom of the toolbox can be seen the current model the values for Toe, Camber and Castor angle for each corner and the total deviation from any defined/open SDF graph user lines. These values are given to assist in later options presented that include running the optimizer to minimize the deviation or auto-setting a part length to match static angles.

Adding an option to a part places a new entry in the column beneath the default option. Each option has the same set of menu options, to modify its label, its value, to remove it from the toolbox, to make the option current or to auto-adjust its length to match the target static value for either Toe, Camber or Castor. Users can thus add as many options as required to Parts with the properties perhaps that reflect the physical alternatives available, and then mix these options to assess overall impact on all relevant suspension derivatives.

As an alternative to adding parts to the top list users can also add graphical elements that themselves control part sizes. These are manipulated in exactly the same way with alternative options.

To make a particular part option current, pick it with the mouse and select the ‘make option current’ menu item. This option will then be shown as indented and in ‘red’.

{bmc bm132.bmp}
Making a Part option current

After a number of part option changes you may require to adjust a tie-rod or toe-link to reset one of the main static angles. To do this pick an option from the required part with the left mouse and select the ‘Adjust Option length to re-set static Toe’. Note that at the end of the menu option is the target static value for this particular angle. Similar menus exist for camber and castor. The current static angles are displayed in the status bar at the bottom of the dialogue box. Obviously using the ‘adjust option length’ on a parts option will change its length property.

The component toolbox utility can be left open whilst the existing model is modified in the normal ways. This can lead to the situation where the ‘baseline’ part options no longer have the correct length properties. If required they can be re-aligned using the local menu option ‘File / Align (All) Baseline Length Properties with Model’. This will reset the baseline option lengths as necessary for all loaded parts.

The internal optimizer can be used to sort through the available part options to identify which combination of options gives the best (lowest) score. The scoring is performed in exactly the same way as the normal optimization process, see The Internal Optimizer. To run through this loop, (in which every permutation is tried), select the local menu item ‘File / Run Optimizer Scoring on Toolbox Options’.

+$#>Overview – Definition Values

The usual way in which a suspension model is modified is by changing part positions or part lengths and then reviewing the resulting suspension derivatives and their static values. Whilst users can use the Data / Set Static Angles menu option to directly set Static Toe and Static Camber all other static values must normally be achieved by manipulating the point positions to achieve a particular required value.

{bmc bm133.bmp}
Setting Static Toe and Camber – Original Approach

This iterative loop is not in keeping with the approach of LSA and thus an additional facility is provided where users can set static angles and offsets directly, the model hard points being adjusted accordingly. The ‘definition values’ options are shown graphically on the model when in one of the three orthogonal views. To turn on use the Graphics / View Definition Values menu option. Depending on the current orthogonal view changes which particular static values can be seen and edited. The static values that can be edited in each view are;

Y-Z plane: (front view)
	Camber Angle, (deg)
	Kingpin Angle, (deg)
	Kingpin Offset (wheel centre), (mm)
	Kingpin Offset (ground), (mm)

X- Z plane: (side view)
	Castor Angle, (deg)
	Castor Trail (hub), (mm)
	Castor Offset (ground), (mm)
	Mechanical Trail (ground), (mm)

X-Y plane, (plan view)
	Toe Angle, (deg)

{bmc bm134.bmp}
Screen shot for the three orthogonal views – Definition values visible

The definition values points are drawn with a small ‘hot spot’ box and the associated value alongside. The ‘hot spot’ is the position to pick rather than the value. Using the ‘hot spots’ these definition values can be edited, joggled or dragged in the same way as any hard point.

The changes to static angles and offsets involves modifying a number of hard point positions. The actual hard points modified depend on the particular definition value and the current settings for that definition values. The particular method used to achieve the required value is changed via the View / SetUp Definition Values display. Each definition value has its own ‘tab’  which identifies if the change method is a translation, axis rotation or complete part rotation. Then a series of relevant sub options are given to define how a axis or part may be rotated.

{bmc bm135.bmp}
Joggling the Static Kingpin Angle

+$#>Overview – Drive Shafts

To extend the compliant analysis capability, drive shaft loads can be included in a simple to use manner. This is done such that rather than users needing to calculate the resulting loads applied to the upright, they can specify gearbox output torques and the drive shaft geometry such that LSA – Shark can determine the actual loads applied to the upright. The drive shaft type that is modeled is one with three shafts and two constant velocity (CV) joints.

The automatic option provided within LSA for adding drive shafts to a model’s template, use menu option Edit / Add to Model / Drive shaft(s), does not add parts and joints to represent the drive shafts instead it adds a number of points and graphics. These points are tagged within the template to be identified as the outer drive shaft centre, the inner drive shaft centre and a point on the inner drive shaft axis. By default when you add the drive shaft the outer CV centre is placed at the currently defined wheel spindle point, (thus no new point is added for this position).

{bmc bm136.bmp}
Drive shaft Added to Model

For full axle models drive shafts are added to both wheels, the second sides’ points having point tag types that indicate they are for the other wheel.

The objective of the drive shaft points are to take a user defined torque,( gearbox/differential output), that is applied to the inboard end of the drive shafts. Using the drive shaft geometry this torque is calculated through the system to identify forces and moments at each joint and hence the forces and moments applied to the upright. Remember that this is a compliance mode calculation and thus you are required to be in compliance mode to view the calculated loads. In addition there is a separate solver switch to enable/disable drive shaft loads, Solve / Drive Shaft Loads, this will be checked when drive shaft loads are included.

The loads applied to the upright include. A fore/aft reaction force at the tyre contact patch, a drive torque along the axis of the stub axle, a torque applied at the outer CV centre and a force applied to the outer CV centre. The orientation of these outer CV forces and torques is dictated by the shaft geometry.

The loads applied to each drive shaft are edited via the Data / Compliance Data / Drive Shaft Torques menu. A single number is available for each corner to allow asymmetric loading effects to be investigated. The sign of the loads is important and is based on the right hand grip rule for the relevant drive shaft inboard axis, (from inner axis point to inner drive shaft centre).

{bmc bm137.bmp}
Editing the Drive Shaft Loads

Joint losses can be included as a function of the joint angle. An optional look-up table is available for each joint listing % loss against joint angle. This is enabled once you define a number of points in the table. To edit the joint loss table select Data / Compliance Data / Drive Shaft Losses…

{bmc bm138.bmp}
Editing Drive Shaft Losses

+$#>Overview – User Defined SDFs

Whilst the number of SDF’s available directly continues to increase with each new release, users will always require the option to create their own. The User Defined SDF dialogue box allows users this option. They are constructed as a semi-formatted text string that the solver can interpret and solve in a structured way. The string can be made up of existing SDF results, point positions, or point forces. Additionally a selection of standard maths functions are recognized and can thus be interspersed within the text string.

{bmc bm139.bmp}
User Defined SDF’s edit display

User defined SDF’s once created are available to be plotted on the x-y graphs or added to any of the text results listings. They are saved as part of the users ini file and can even be shared with other users via an external data file transfer.

To create a new SDF select the ‘Add’ button, this will increase the counter by one a display a default title and an empty function string. Set the title as required.

To add a field to the function string either enter directly or use the supplied selection boxes to locate required field. Note that square brackets [ and ] are used extensively to identify the start and end of a field. Available fields are grouped into a number of sections;

	Standard SDF’s,  example [Castor Angle]
	Front Point by Label,  example [Lower wishbone front pivotX]
	Rear Point by Label,  example [upper wishbone rear pivotZ]
	Front Point by Number,  example [frontP2Y]
	Rear Point by Number,  example [rearP5X]
	Front Graphic,  example [frontG3]
	Rear Graphic,  example [rearG1]
	Front Force by Label,  example [Outer track rod ball jointFZ]
	Rear Force by Label,  example [Inner track rod ball jointFR]
	Front Force by Number,  example [frontP6FY]
	Rear Force by Number,  example [rearP1FX]
	Point type,  example [Twheel centreY]

Fields are built up into more complex functions using the supplied maths functions, such as +,-,*,/. For more complex functions the standard brackets, ‘(‘ and ‘)’, should be used to confer solution precedence. Other trigonometric maths functions such as COS, SIN, TAN etc are available in both degree and radian forms.

An example of a fictitious function string might be;

	COSD([TWheel centreX]/[frontG8])

A subset of supported maths functions are specifically aimed at vector calculations. They all start with the letter ‘V’ to indicate this. Some produce a vector output whilst others produce a scaler output. Vector functions should only use vectors as arguments, (see example below).

VCROSS([Wheel spindle pointV],[Wheel centre pointV])

+$#>Overview – Control Elements

Control elements provide users with the opportunity to change a part length or point position with an actuator. The actuator changes the selected property using a sensor. The sensor returns the change in length of a specified point to point distance, (e.g. damper length), and based on a look-up table identifies the required actuator change.

As indicated above two actuator types are available, the ‘Length Actuator’ and the ‘Position Actuator’. The length actuator replaces the fixed length between two points, (which must be on the same part), with a varying length element. The position actuator turns a hard point, (which must be attached to ground), plus an optional additional point, (e.g. on a wishbone both attachment points to ground), into a point(s) that can be moved along a particular defined axis.

{bmc bm140.bmp}
Adding a Control Element- menu options

To add a length control element to the model, use the appropriate menu and select the two points that define a distance you wish to replace with a length actuator. The graphics will change to reflect the addition of the actuator, (note that by default the input sensor distance for the added actuator will be set to the damper1 points.

{bmc bm141.bmp}
Length Control Element added to Lower Wishbone

The relationship between the change in length of the transducer and the actuator is defined in a look-up table the values for which can be edited, (as well as the other properties such as transducer points), by editing the element in the same way as you would for any graphical element, change to edit mode and select the length transducer ‘hot spot’.

{bmc bm142.bmp}
Editing Length Actuator Properties – Table and transducer points indicated

To add a positional control element to the model select the appropriate menu and then pick the relevant hard point, (remember that it must be attached to ground). By default the optional second point is not added and the motion vector is aligned along the y-axis.

{bmc bm143.bmp}
Position Control Element added to Upper Wishbone, single point and second point shown

The properties of the positional transducer are edited in the normal way, in ‘edit’ mode pick the transducer. This allows you to change the secondary position, the vector and the look-up table.

{bmc bm144.bmp}
Editing Position Actuator Properties

Because of the potential for solution instability, control elements have a one step delay. This means that they use the length change of the previous calculation step. This may be an issue when running the solver in combined mode with large jumps between successive points.

+$#>Overview – Spacers

Spacers can be added to a model in the same way that they are used in a motorsport application. They are added either to a point between parts, or at a point to ground. Spacers have a length property and an initial vector orientation. Spacers can be included in the ‘Component toolbox’ utility and thus have length options created for them and used to adjust static settings. They can also be modified via the standard edit, joggle and drag options.

{bmc bm145.bmp}
Adding Spacers – Menu Selection

To add a spacer to the model select the appropriate menu option, then select the part you require to add the spacer too, (pick the part centre). The display will change to just show the selected parts and its points. Now pick the part you require to add a spacer too. You are then prompted to define the initial orientation of the spacer in global co-ordinates.

{bmc bm146.bmp}
Setting the Spacer Global Orientation

For some instances such as wishbone pivot points, the application will identify that there is a second point that is associated with this connection, (i.e. for a suspension wishbone the two pivots points would be considered as associated), and you are given the option of including the this associated point with the spacer. Points connected in this way will work as a pair such that you only need to change the length property for one and this is reflected in the other. This is required if the original part is to remain correct, since changing only one spacer on a wishbone would lead to a corruption of the original parts geometry, (i.e. it is no longer the same part).

{bmc bm147.bmp}
Including the 2nd Point for a Spacer

Finally you are asked to define the initial spacer length.

{bmc bm148.bmp}
Setting the Initial spacer Length Property

Once a spacer has been to the model it is drawn as a cylinder with its length property drawn and an arrow indicating the orientation vector.

{bmc bm149.bmp}
Spacer to Ground Added to Wishbone Pivots – Secondary point Shown

To edit the properties of the spacer either drag/modify the associated vector to re-define the orientation. To change its length either change to edit mode and select the spacer graphic in the normal way or you could joggle the length when in one of the relevant ‘change modes’.

{bmc bm150.bmp}
Editing the Spacer Properties – Spacer Length Shown

+$#>Overview – Batch Mode

Normal use of the Shark module of LSA is via the full graphical interface. Within the application is support for a ‘batch’ mode. Use of the batch mode can vary from within the graphical interface running a script file in batch mode through to running the entire application in batch mode.

The Batch mode uses user entered text commands rather than graphical menu selections, and it is these graphical commands that can be buffered into a simple ASCII text file and then used as a ‘script file’. Most relevant pull down menu entries in the graphical interface have an equivalent batch short text command. Batch commands are also arranged into groups that match the pull down menu groups. For example the main pull down menus are arranged under File, Module, Data, Edit, View, Tracking etc. and the batch commands are grouped in the same way.

A short 2/3 letter text syntax is used for the batch commands. So for File you would type FI, for Module you would type MO. Note that because of duplication not all commands are simply based on the first two characters of the full menu and example of this is that for Graph you would type GP as GR is already used for Graphics.

{bmc bm151.bmp}
Example Batch Commands- Top level commands shown

Special text commands are available to migrate up a command level ‘/’ list a description of the current available commands ‘?’, quit the application ‘QU’. Batch commands can also be strung together such that the equivalent of the pull down menu File / New  would be FI NE. Some batch commands also support arguments, the case of the File / New (FI NE) command is one of these. Where it does support additional arguments the ‘?’ listing will indicate this as bracketed terms [ ] after the menu command, (see below).

{bmc bm152.bmp}
Example Optional Arguments – File / New example shown

To open the application in Batch mode use the appropriate desktop shortcut icon. This should have been added as part of the install and labeled as ‘Shark (Batch)’. The properties of the shortcut are set such that the command line argument has the string ‘BATCH’ added to it. This then causes the application to open in Batch mode.

{bmc bm153.bmp}
Desktop Top Icon Properties – ‘Batch’ argument ringed

The batch mode display opens as a simple scrollable text window. It will open in top level and wait for commands to be entered. You can switch at any time into the full graphical interface by entering INT at the top level.

The batch mode can also be started from within the graphical interface via the appropriate menu File / Manage Batch Files / Open Batch Command Window…

{bmc bm154.bmp}
Opening the Batch Command Window from the Interface

Batch commands can be assembled into an ASCII text file and run as a script file. Thus complete procedures can be fully automated. It is important with script file to ensure that commands placed on subsequent lines have sufficient ‘/’ characters to return to the top level before moving down another command tree. An extract of a simple script file is shown below.

{bmc bm155.bmp}
Example Script File – Batch commands used

This script file illustrates the use of the ! character to indicate that this line is a comment line, it then uses the File / Open command with the optional Filename argument. If the filename had been omitted a file browser would appear to prompt for the missing argument. The ‘//’ lines are inserted to ensure the position is moved back to the top level prior to moving down a different command tree. The SO BU command runs the solver in bump articulation, whilst the final line lists the Fitted SDF Results.

A simple tool is provided to allow the user to manage script files. To add, remove, edit and run from a single dialogue box.

{bmc bm156.bmp}
Managing the Script Files from within the Interface

For a full list of the supported batch commands and their equivalent short string see Batch Commands

+$#>Overview – User Language

The default language for the interface of Lotus Suspension Analysis is English. An option to switch the language to a user defined set is made through the menu SetUp / Language / User defined. This setting is saved to your INI file. To take full effect the application needs to be restarted.

Please note some customer sites have a customized approach to the editing and storing of the custom dictionary and may thus differ from the locations and approach outlined here. They may also be protected by a local password file, (please refer to your local system support).

The user defined approach allows for as many (or as few) “string” elements to be defined. It is applied on a string by string replacement basis. Thus a user would need to create this library from user input. The user-defined library is stored in the file “_Custom.dic” which is saved to the startup folder.

The editor in the software, allows the authorized user to sort through each string entry and enter a replacement. The entries are given a short and a full equivalent. Normally only the ‘short’ string is used. The full menu is a guide to indicate where it is used. Some common words appear in both the UPPER case and lower case if not part of a menu.

Search provides a way of find/repeat default English words. If an entry is left blank the English word is used, thus only partial language definition can be implemented or added to at a later date.

{bmc bm157.bmp}
Editing the user language Entry for Camber Angle

+$#>Overview – Reports

‘Report Files’, are script files that allow a user to formulate the process of generating consistent reported output from the program. They rely on batch commands and batch files so users should be familiar with these. By combining the functionality of batch commands with additional format statements such as ‘new page’ different report formats can be merged into a single report document. In a similar way to batch files report files are run, edited and managed through a utility tool. Report files can be shared between users either through common file location or local copies of the same files. ‘Standard’ report files can added to interface menus and lists by and these lists are saved as part of the INI file. Reports created in this way can be sent straight to printer or file, alternatively they can be displayed in a rich text editor that provides the opportunity to edit/format the content before printing.

{bmc bm158.bmp}
The Reports Display

Report files are used to standardise and streamline the process of producing reports from the suspension analysis. They make use of batch commands and files to load solve and list results, whilst additional formatting options such as line feed and new page are included to allow the creation of ‘standard’ report formats.

Report files are ASCII text files which whilst they are similar in form to Batch files have some specific layout and formats and thus would not normally be edited through a simple ‘text’ editor. The interface provides a ‘mange’ tool just as with batch files but the edit option opens a unique spreadsheet editing tool.

As mentioned above report file can reference existing batch files, whilst in turn batch file can run/reference report files so users should ensure that recursive loops are avoided.

Report files are made up of a sequence of lines, each line defines an action a result or some other relevant action. The following list the available items and their associated arguments.

Single Line of Text: Adds a single line of text to the report document. Arguments are; text string, font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Line Feed and Font type.

Text file: Adds the contents of the supplied text file to the report document. Arguments are; file name, font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Line Feed and Font type.

Single Blank Line: Adds a blank line (hence implied line feed) to the report document. No arguments.

Single Space: Adds a single blank space to the report document at the current position. No arguments.

Single Character: Adds a single character to the report document at the current position and using the current font attributes. Single argument, the Character.

New Page: Adds a page break to the report document. No arguments.

Single Batch Command Line: Performs a batch command or series of batch commands. It does not add results to the report, it just allows for the required data changes, solver changes etc that may be required to enable the required results to be subsequently included. Arguments are; batch command string.

Batch Command File: In the same way as the ‘single batch command line’ this does not add results to the report. The defined batch file will contain command strings necessary to make data changes solver changes etc, so that the required results can subsequently be added to the report. Arguments are; batch command file.

Formatted SDF: Includes the specified corners Formatted SDF results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number and format set number.

SDF Spline Fits: Includes the specified corners SDF Spline fits results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number and format set number.

SDF Spline Data: Includes the specified corners SDF Spline data results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number and format set number.

Bush Deflections: Includes the specified corners Bush Deflection results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type and Corner number.

Joint-Bush Rotations: Includes the specified corners Joint-Bush Rotation results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type and Corner number.

Bush Forces: Includes the specified corners Bush Force results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type and Corner number.

Formatted Point Forces: Includes the specified corners formatted point force results in the report document using the defined format set. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number and format set number.

List All Point Coords for User Position: Includes a list of all points for the specified corner at the defined user position. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number, bump travel, steer travel and roll travel.

List a Point Coords at All Positions: Includes a list of specified point for the required corner at all current solution points. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number and Point label (or point No.).

List All Point Coords at a Position: Includes a list of all points for the specified corner at the identified position. Arguments are; font colour, font size, Bold on/off, Italic on/off, Underline on/off, Strikeout on/off, Superscript on/off, Subscript on/off, Justify, Font type, Corner number and Position label (or position No.).

Insert User Window: Inserts a user window/control as an embedded image in the report. Arguments are; User Window No. (or User window label), Line feed and Justify.

Insert Visible Graph: Inserts a visible graph as an embedded image in the report. Only currently open graphs are available, so batch commands will need to be used to ensure they are open before being included. Arguments are; Graph No. (or SDF Label), Line Feed and Justify.

Insert Current Graphics: Inserts the current graphical view as an embedded image in the report document. Arguments are; Line Feed and Justify.

Insert Current AVI as File: Inserts the current animation sequence as an embedded AVI object in the report document, (included like this within a word document it can be viewed/animated directly from Word when the document is distributed). Arguments are; Line Feed and Justify.

{bmc bm159.bmp}
Editing a Report File

Report files can be run from within the application whilst in ‘Command Mode’ (not to be confused with the Windows Command Prompt). For example you would enter the following short command, RE RE RU report1.rpt or RE RE RU <install>report1.rpt

The Run (RU) option does just that in command mode, it will only run the report file. If you want to subsequently view the report file you will need to open the rich text display (DI) or to print the current report select the print (PR) command. Note that you can give both the display and print commands an optional filename so that it will open or print using the new report file. (Note that display and print does not currently support file number it must be the file name).

The application provides a list of standard ‘report’ files. These can be added to/organised via a tool in the main graphical interface. In the command mode you can list the standard files via the RE RE LI short string command. They are listed by number and can then be run either by using the filename or more simply by its number, (see comment above on display and print options).

Within the command mode options are provided to browse (BR) for a report file, list (DIR) current directory contents or change (CD) the current directory. Note that for specific server based installations the use of the ‘<install>’ string is supported as part of the file name where ‘<install>’ is automatically replaced by the software with the actual software installation folder location.

Printing is control by local printing properties which can be edited through the local printer setup (SE) command.

Report files can be run directly from the Results menu. In the same way as with running in command mode a list of ‘standard’ report files is given together with the option to browse for a file. Running a results file from the graphical interface will cause the ‘results report’ rich text display to be opened and the created report document displayed.

Once the report file has finished the displayed report can be edited using the functionality of the rich text editor. Alternatively it can be sent to a printer, saved to a rich text document or opened directly in Word.

To add an existing report file to the defaults list either use the main menu option Results / Manage Report Batch Files / Add File to List…and use the browser to locate the required file or from the same sub menu open the Report Batch File List Status…

The ‘Report Batch File list – status’ display allows you to add other report files in the same way as the previous item via a conventional browser. It also provides access to a number of other report file features. These include changing the order of the files in the list, Remove (All) file, Edit a file from the list, Run a file from the list or create/edit a new report file.

{bmc bm160.bmp}
The Report ‘status’ Display

+$#>Overview – Flexible Parts

The basic compliant module within LSA is based around rigid parts joined to each other by 6 dof bushes. A rigid part is usually taken as the complete part i.e. a wishbone, arm or upright. This concept of rigid parts can be extended to consider an individual suspension link as being made up of a sequence of rigid parts again connected by bushes. In this way the structural flexibility of a suspension link can be modeled by converting the single part to a series of ‘meshed parts’.

A part meshing tool is available that will automatically convert a single part to a user defined group of parts. This involves changes to the template which are made by this utility as part of the ‘meshing’ process.

The template modifications include the use of special tags to indicate that these points and parts are purely for compliant use. This is so that the kinematic solution is not burden with any additional constraint equations, only the burden of post calculating the new kinematic positions of the mesh node points is involved.

Parts to be meshed need a minimum of three ‘connection’ points to enable them to be meshed using this utility.

The utility, Edit / Mesh Rigid Part, needs the user to pick the required part and the three points on the part. The mesh is applied from the vector between the first two points, progressing towards the third point. Thus the new meshed parts are four-sided with the last mesh being triangular. The meshed parts compliant connections rather than being at the ‘nodal’ points’ are made via a third point placed mid way between the two nodal points. This is to allow the flexibility of the part to be defined more in the style of a series of ‘beam’ elements than actual plate style finite elements.

The screen shot below shows the lower wishbone of a conventional double wishbone suspension that has been meshed from the inboard pivots out to the lower ball-joint with six meshed parts replacing the original one part.

{bmc bm161.bmp}
Flexible Part - Example

Each connection between the mesh parts is made by three points, two of them are ‘tagged’ in the template as ‘zero stiffness mesh point’ and the third point is ‘tagged’ as the ‘structural mesh point’. The compliant solver then adds a zero stiffness bush at the first and uses the default rigid stiffness values for x, y and z and the default value for compliant rotation stiffness for x-x, y-y and z-z. These can be individually re-defined by the user in the same way as any other bush.

It should be noticed that when you mesh a part the connection of the suspension spring will be modified if it was attached to the original part prior to meshing. Its connection is moved to the nearest part, (note that the co-ordinates of the connection are not changed only the associated part). If you subsequently alter the spring attachment points position, it will still be associated to the original nearest meshed part. Thus it may be necessary to re-assign the associated part to reflect the new position.

+$#>Overview – Interactive Template Builder

Most users will find that LSA with its 30+ standard templates will have one that suits their requirements. There are cases where you may wish to make small changes to templates to meet a particular requirement. In the first instance these simple changes can be incorporated using the range of ‘Edit’ menu options provided that enable points, graphics and standard items such as roll bars to be simply included.

For users wanting to make greater changes or need to build a template from scratch the 3D template builder module provides a fully interactive tool for adding parts, making connections etc. The alternative to the Interactive method would require using the template spread sheet tool, File / Edit Templates. The two methods are interchangeable in that you can work in both interactive template mode and then review settings in the spread sheet, make changes as required and then return and continue in the interactive template module.

To enter the interactive template builder mode select the Module / Shark / 3D Template Builder menu. Alternative pick the equivalent icon from the Template builder toolbar. These toolbars by default are turned off. Use the SetUp / Toolbar Visibility menus to make the two Template Builder Toolbars visible.

Once In the Template builder mode the graphics display changes to indicate this change showing the ‘Template Builder’ text around the periphery. The display also includes a series of selectable lists for ‘Tag Type’ ‘Points’ ‘Parts’ ‘Graphics’ and ‘Status’. Each of this lists can be moved, re-sized or have their visibility toggled on and off. The lists also provide a series of ‘hot spots’ that enables position sensitive right mouse pop-up menus.

To start building a new template select the File / New menu in the normal way…  Then select if this is going to be a steerable, non-steerable or copied from an existing template.

{bmc bm162.bmp}
New Template Menu

You are also offered the chance to specify the label for this new template, (note that the label entry dialogue indicates the slot number that the template is using.

{bmc bm163.bmp}
New Template Label Entry

You can now start to build your new template adding parts by selecting the relevant icon from the ‘parts bin’ toolbar. You then join parts together by merging two points or attach a part to ground a selected point. These builder ‘actions’ are available either from the second template toolbar or through the Edit / Template Builder Actions menu entries.

The current builder actions include;

Join Part to Part (at Mean of Two Points)
Join Part to Part (at Point 1)
Join Part to Part (at Point 2)
Join Point to Part (at the Point)
Join Point to Ground (at Point)
Split Parts (at Point)
Split Part from Ground (at Point)

Once Parts and Points have been added to the template, additional builder actions are available through the context sensitive right-mouse menus. These include:

Delete Point
Delete Part
Delete Graphic
Flip this Parts Points in Y
Mirror this Part across in Y

The normal process of building the template is to add parts, join them together as required, whilst checking the number of unknowns and number of equations shown in the ‘status’ section. Once all parts/points are added (and assuming the no. of equations equals the no. of  unknowns) then the final stages of the build is to add any extra graphical elements for visualization and ‘tag’ any points that may have special functions, such as ‘lower ball joint’, ‘steering attachment’ etc.

At this stage the template can be used by simply switching to one of the ‘active’ 3D modules, such as 3D Bump but it is good practice to ensure you save the template first using the File / Template File options sub-menus.

+$#>Getting Started – Start-up Steps

Starting the program can be considered to consist of the following steps;

1) Start the executable, locate either from the Start menu, (normally Start / Programs / Lotus Engineering Software / Lotus Suspension Analysis), or through explorer. Browse to the installed folder (normally c:\lesoft), and run the suspension analysis executable shark.exe. (note that an alternative executable sharknonVc.exe is also available that whilst identical in functionality/results etc. does not make use of virtual memory and is sometimes required rather than the default virtual common version.)

2) Select the solution module required from either 2D or 3D, and the required articulation type. The default is to open in the 3D module under bump/rebound articulation.

3) Set the required display units.

4) Optionally load any required user defined templates.

5) Enter the required suspension data, either from an existing saved file or through the new file options. 

{bmc bm164.bmp}

+$#>Getting Started – Program Start-up

During program start-up a number of system checks are performed. The users ini file is searched for and if found, loaded to overwrite the internal defaults. User line data bases if referenced are also checked for and added to the relevant menus.

+$#>Getting Started – Start-up Errors

During program start-up the searching for a subsequent loading of the users ‘ini’ file can in exceptional circumstances, results in an error message. This implies a corrupt ini file possibly due to a previous partial save or inappropriate editing, (the ini file should not be edited by hand).

{bmc bm165.bmp}
Error message ini file read failure

Selecting okay will continue to start the program, but with only a partial reading of the ini file, (partial up to the point of read error). Partial reading of the ini file may cause problems which may require the program to be closed and restarted. If the problems persists, (as it may, since the invalid settings will be written back into ini file when the program has a normal exit), the only option may be to delete the ini file, see Defaults.

Whilst strictly not a start-up error, the other possible start-up event that may occur is the detection of a previous runs temporary scratch file. This is interpreted as a previous run incorrectly shutting down, as these temporary scratch files used for the undo feature, are deleted on normal program exit.

If a scratch file(s) is identified, the user is given the option of recovering the one before the most recent file and thus avoids potential data loss. The reason for selecting the one before the most recent rather than the most recent, is that this may simply re-apply the same conditions that caused the original crash.

{bmc bm166.bmp}
Data Recovery Message

+$#>Getting Started – Graphics Frame Types

The interfaces main graphics display has two alternative drivers. The default device driver is a Windows GDI, (Setup / Graphics Frame Type / Windows GDI), which whilst it works with all Hardware options does so at the expense of both speed and capability. The GDI driver is unable to support depth buffered display and hence the view styles View / Fill Style / Hidden Line and View / Fill Style / Depth Buffered (Flat shaded ) do not function correctly. The alternative device driver is Open GL, (Setup / Graphics Frame Type / Open GL), which is both faster and supports depth buffering/hidden line display types.

Not all hardware is able to use the Open GL device type, typical failures are inability to refresh and lack of correct hidden line display. This can normally be fixed using the two options Setup / Use Segment Display and Setup / Use Software Double Buffer. Alternatively some users may wish to resolve  issues by changing the level Hardware acceleration used by the graphics card. Moving towards ‘None’ in incremental steps can identify how much hardware acceleration can be successfully used.

The OpenGL graphics frame is preferred not just because it enables shaded image displays to be used, but also because it provides the option of using the ‘Segmented Display’ option, (menu Setup / Use Segment Display). Segmentation significantly improves animation and viewing refresh speeds since rather than having to re-calc and redraw all the graphics primitives only the viewing matrix is refreshed and then the existing saved graphics segment re-drawn.

+$#>Getting Started – Window Descriptions

The application window layout utilizes a Multi Document interface (MDI) style. Where display and graph windows are displayed as children of the main window. The main window has a top menu bar and four toolbars which have optional positions. The graphical display is drawn in a 3D viewing window, whilst individual graphs have separate windows.

{bmc bm5.bmp}
Example screen shot – Overall appearance of application

+$#>Getting Started – Module Type

On program start-up by default the application will go into the 3D module, and in bump/rebound articulation mode. Since the 2D and 3D module data sets are completely separate, change to the required module before starting data entry.

{bmc bm167.bmp}
Setting the application module – Toolbar Icons

The menu entry Module / Shark sub menu can be used to select the required module and articulation type.

{bmc bm168.bmp}
Setting the application module – pull-down menu options

Note that it is possible for the application to detect that a data file being loaded is a 2D or 3D data file and if necessary it will switch to the appropriate module.

+$#>Getting Started – Data Entry

At start-up the main form of data entry to the program is the suspension hard points coordinates, (irrespective of module). To load an existing data file use the File  / Open... menu item, (note that the five most recently opened files are appended to the File menu). To create a new model select the File / New menu item set the required suspension end(s) to model and the required suspension type. All new models created in this way will be fully populated with default values, not only for the suspension hard points but also all other data requirements, (i.e. tyre sizes).

{bmc bm169.bmp}
Creating a new model

These default values can now be edited whilst still within the ‘new model’ dialogue box by selecting the relevant icon. Alternatively the ‘Done’ option can be selected to view the new model and the main ‘Edit’ functions used to revise the data.

{bmc bm170.bmp}
Editing the default co-ordinates data

It is possible to have an asymmetric model. If this is required then the check box at the top of the ‘new model’ dialogue should be un-selected. This switch between symmetric and asymmetric (and back again) can be applied at any time not just at the creation of a ‘new model’. To do this simply pull up the ‘new model’ dialogue box and change the setting of the ‘Symmetric Suspension’ check box, no existing model data is lost by this change other than the asymmetric information if switching to symmetric.

Should it be preferred users can select to have the default for a single corner model to be in –ve Y rather than the default +ve Y. The check box at the top of the ‘new model’ dialogue box can be selected if this is required.

+$#>Getting Started – Exiting the Program

The close the program select the File / Exit menu item, and then confirm the ‘okay to exit’ prompt. Alternative methods to close the application include the conventional ‘X’ from the windows top right corner, Alt+F4 or close from the main windows top left menu. In addition the ‘esc’ key will close the application, (subject to accepting the prompt).

{bmc bm171.bmp}
Okay to exit prompt

+$#>Pull Down Menu Items - File

File / New: Creates a new model. Opens the new model dialogue box to create a new suspension model. This is also the route to adding a new front or rear suspension to the current model file, i.e. convert a single axle model into a full vehicle model.

File / Open: Opens the standard Windows file browser to locate the required existing file to load. Note that file open will lose the current model data. The file reader is able to identify the difference between a 2D and 3D data file and will if necessary change module.

File / Close: Closes the current model, but leaving the application open.

File / Add End from File: Opens the standard Windows file browser to locate the required existing file to load the suspension end from. This 3D only option allows the user to add to a single end model the other suspension end from an existing saved file. Only the suspension geometry and compliance properties are loaded from this second file. You cannot use this option if you already have both ends defined. If you have a full vehicle model and want to switch one end to a saved model you must first remove one the required end by using the File / New menu and un-checking the relevant selection box.

File / Import Hard Points from / Adams Sub System: Opens a split screen text editor window that allows the user to load an Adams Sub System model file and extract the hard point geometry directly from it via text recognition strings defined in the template. A preview feature allows the identified Sub System sections to be viewed and the hard point values found.

File / Import Hard Points from / User ‘A’ Format: Opens a split screen text editor window that allows the user to load an User specific model file and extract the hard point geometry directly from it via text recognition strings defined in the template. A preview feature allows the identified Sub System sections to be viewed and the hard point values found.

File / Export Hard Points from / Adams Sub System: The reverse of the previous Adams menu item. Opens the same split screen text editor window that allows the user to load an Adams Sub System model file and populate it with the current hard point geometry directly to it via text recognition strings defined in the template. A preview feature allows the modified Sub System to be viewed prior to applying the extraction.

File / Export Hard Points from / User ‘A’ Format: The reverse of the previous User A format menu item. Opens the same split screen text editor window that allows the user to load a User specific format model file and populate it with the current hard point geometry directly to it via text recognition strings defined in the template. A preview feature allows the modified Sub System to be viewed prior to applying the extraction.

File / Save: Saves the current model to the originally opened file name or the latest subsequent Save As file name.
 
File / Save As: Opens the standard Windows  file browser to enable the current model to be saved to disc. Browse to the required folder and enter/select the required file name.

File / Auto Search and Load / Off: The Auto search and load utility provides a method by which an external application can automatically update the hard point position of points in the current model. For the defined event timer the shared data file is checked for and if modified since last read is opened and data scanned for. If the scanning successfully identifies a point by its text ‘label’ and associated coordinates values found then these new positions are applied to the model. This auto-search and loading behavior is controlled by a number of menus, (see below). They control if this feature is on, whether to prompt before loading data changes, where to look and how often to look. This particular menu switches the auto search to ‘off’. The text label matching is based on the point labels as set in the template. In addition the ‘Adams Import Point Label’ is also used in the attempt to identify a match.

File / Auto Search and Load / Scan Once: Performs the Auto-search and load function once only based on the defined file name.

File / Auto Search and Load / On – Prompt before Load: Turns the Auto-search and load function on. At the currently defined time interval, the specified file is searched for and if modified since last read new values will be loaded but only on user confirmation.

File / Auto Search and Load / On – Auto Load: Turns the Auto-search and load function on. At the currently defined time interval, the specified file is searched for and if modified since last read new values will be automatically loaded in with no message given to the user.

File / Auto Search and Load / Edit Timer…: Opens a simple edit box to allow the auto-search timer interval to be edited. Default setting is 3000 mSecs.

File / Auto Search and Load / Edit File Name…: Opens a simple edit box with browser icon to allow the auto-search file name to be edited.

File / Re-Read Default Templates (Skip All User): This menu option will remove all currently defined templates and revert back to the hard coded default template definitions. The user templates file is not loaded even if it exists.

File / Re-Read Default and All User Templates: This menu option remove all currently defined templates and revert back to the hard coded default template definitions. It will then search for and if found re-read the data file that contains the user defined additional 3d kinematic template information. It is defined as additional since the original hard coded templates are always available, (unless overwritten by the external defaults file or a user loaded set).

File / Add Custom Templates from File: This option allows a user to read a separate templates file. This file can either add to or overwrite the currently defined templates. This potential to overwrite includes both the hard coded defaults and any loaded from the ‘users’ file. Templates are identified by a position index, thus if you load a template as index 4 it will replace the hard coded default template.

File / Edit Templates: Opens a multi-panel spread sheet display that allows the user to edit and create templates. The user can view the settings of the existing templates, (including hard coded templates) and use the existing templates as a start point for a new template.

File / INI Files / Re-read <install> INI File: Re-read the INI file and it associated settings from the <install> folder. The <install> folder is the location of the original executable.

File / INI Files / Save INI File to <install> Folder: Writes the INI file and the current settings to the <install> folder. The <install> folder is the location of the original executable. The access rights are as set by the local admin rather than the application.

File / INI Files / Re-read <database> INI File: Re-read the INI file and it associated settings from the <database> folder. The <database> folder is set either by a local variable or the setting in the <install> INI file.

File / INI Files / Save INI File to <database> Folder: Writes the INI file and the current settings to the <database> folder. The <database> folder is set either by a local variable or the setting in the <install> INI file. The access rights are as set by the local admin rather than the application.

File / INI Files / Read INI File from…: Read an existing INI file from a user selected location.

File / INI Files / Save INI File to…: Writes the INI file and the current settings to a user selected location and file.

File / File Text Edit…: Opens the Data file text editor. This dialogue box can be used to view and edit data files in a purely textual environment. This is an advanced user feature only that is primarily intended for debugging use and is not recommended as a normal working practice. This is primarily because the data file format is not formally declared. 

File / Run Batch File / Browse for File… Opens the file browser to allow the user to locate and run a batch file. Selecting a batch file will open the Batch file dialogue box to which all batch commands in the file will be echoed along with any batch output. Appended to this menu will be a list of batch files already added via the ‘Manage Batch Files’ command, (see below).

File / Manage Batch Files / Add File to List… Opens the file browser to allow the user to locate an existing batch file, once selected it is added to the ‘Run Batch File’ menu, (see above).

File / Manage Batch Files / Batch File List Status… Opens a dialogue box that lists the current batch files available from the menus. From this dialogue box batch files can be added and removed.

File / Manage Batch Files / Open Batch Command Window… Opens the batch command window. This allows a batch session to be performed. Having been opened from the graphical interface graphical changes made to the model will still be seen. This is unlike when the application is opened directly into batch mode where no model graphics are visible.

File / Set Batch Record Control Keys…: Simple selection display to identify which keys are used to Start, Pause/Resume and Stop the recording of key strokes entered into the text window whilst in the command mode. Recorded key strokes can be saved to a text file for later use as the basis of a batch file.

File / Run Report Batch File..: Either browse for or select from the list a ‘Report Batch File’. These batch files contain a sequence of commands that replicate user entry to load models run analyses and compile a report containing the specified data and results. The resulting report text file is loaded into the report viewer for subsequent viewing, editing and printing.

File / Manage Report Batch Files / Add Report File to List..: Use the standard file browser to locate report batch files that are added to the file list for the preceding menu entry.

File / Manage Report Batch Files / Report Batch File List Status..: Opens the report batch file status display that enables the user to manage the file list and run selected report files. The run options for the produced report file include displaying, write as rich text file, open in word or directly print.

File / Manage Report Batch Files / Open Report Display Window..: Opens the reports display window. This scrollable rich text display will contain the last report file generated, (if any) and enable it to be viewed, edited or printed.

File / Exit: Closes the application, subject to confirmation of ‘okay to exit’.

Appended to the bottom of the File menu, is a list of the last five (max) opened files.

+$#>Pull Down Menu Items – Module

Module / Shark / 2D Bump: Changes to the 2D module in Bump articulation mode.

Module / Shark / 2D Roll: Changes to the 2D module in Roll articulation mode.

Module / Shark / 3D Template Builder: Changes to the 3D template builder module.

Module / Shark / 3D Bump: Changes to the 3D module in Bump articulation mode.

Module / Shark / 3D Roll: Changes to the 3D module in Roll articulation mode.

Module / Shark / 3D Steer: Changes to the 3D module in Steer articulation mode.

Module / Shark / 3D Combined Motion: Changes to the combined Bump, Roll and Steer articulation mode. This allows a user defined combination of bump travel. roll angle and steering lock to be specified for analyzing items such as ball joint travel and wheel envelope

Module / Raven / STD Interface: Changes to the Raven module. This will only be available if you are licensed for this full vehicle-handling module, (licensed separately from Shark).

+$#>Pull Down Menu Items - Data

Data / Model Properties: Edit model properties via the tree structure display window. Expand required sections to locate individual data fields. Select required data field and edit displayed value.

Data / Point Coordinates / Use Open List: This option when checked uses the alternative ‘open’ point coordinates listing display. This ‘open’ display can be left on screen throughout the program use. When unchecked point list/display reverts back to the original ‘close before continue’ display.

Data / Point Coordinates / 2D: Displays 2D model coordinates for viewing and editing in a simple single column spread-sheet, (only available in 2D module).

Data / Point Coordinates / Front: Displays 3D model front coordinates for viewing and editing in a multi column spread-sheet, (only available in a 3D module with a front axle included).

Data / Point Coordinates / Rear: Displays 3D model rear coordinates for viewing and editing in a multi column spread-sheet, (only available in a 3D module with a rear axle included).

Data / Point Tolerances / Point Tolerance Analysis: Performs a Tolerance analysis for the specified point. Open graphs indicate the range of displayed variable due to the limit box size.

Data / Point Tolerances / Set Tolerance Point: Set the suspension hard point to be used for any subsequent Tolerance analysis.

Data / Point Tolerances / Edit Point Tolerances: Lists the model hard points in a ‘tree’ type view environment, to locate the required point and view/edit its current limit box settings. Limit box settings define the allowable +/- distances along each axis from the defined position.

Data / Point Tolerances / Set All Point Tolerances to…: View/Edit routine to set all suspension hard points to the same values in one go. Opens a simple edit box with six values, one for each tolerance –x, +x, -y, +y, -z, +z. These will be applied to each point in the model.

Data / Point Tolerances / Solve Mid Point: This switch controls whether the points at the middle of each side of the tolerance box is included in the tolerance positions. When unchecked only the corner points and the original position are solved for.

Data / Parameters: Lists the ‘Parameters’ data set for viewing and editing. This data set includes the values controlling the articulation limits, overall vehicle properties such as wheelbase, C of G height, brake split, drive split and brake type.

Data / Raven Conversion Parameters: Lists the static values used when populating the virtual SKCMS data file. These single values are not calculated as part of the test nor are they part of the Shark data file, hence these editable default values are used.

Data / Raven Corner Parameters: Lists the corner values used when populating the virtual SKCMS data file. These corner values are not calculated as part of the test nor are they part of the Shark data file, hence these editable default values are used.

Data / Body Type: Defines the body graphics used in the 3D display. Options currently limited to the internal options or none. Envisaged expanding to include user defined body sets. Current options include, none, Saloon, Open sports, Old Single Seater, Single Seater, Utility, Super Saloon, Minivan and user defined. Select the required option. Visibility controlled by separate visibility switch.

Data / Edit User Body Data: For the user defined body option this menu is enabled to allow direct editing of the lines and facets used to define the body. This allows existing default types to be modified and/or import of STL files to represent the body.

Data / Tyre Sizes: Lists the ‘Tyres’ data set for viewing and editing. In kinematic mode this lists the rolling radius for the front and rear axles, together with the width. The tyre width value is purely for graphical visualization, it does not alter the analysis results. When in compliant solver mode two additional values are listed, these being the tyre vertical stiffness settings.

Data / Steering Type: For front suspensions this defines if the steering mechanism is a rack or one of the two steering box types. The steering box systems require additional hard points to be defined. When first changing a model from rack to steering box, the application will prompt for the coordinates of the steering box.

Data / Steering Type / Edit Box Coords…: Only enabled when steering type is set to one of the ‘steering box’ types. This displays the current steering box hard points coordinates in a simple spread-sheet display. For an asymmetric model both sides are given.

Data / Steering Type / Edit Rack Pinon Radius…: This displays the current steering rack pinon radius value. This value is used to derive hand wheel angle from rack travel and derive hand wheel moments from rack axial forces.

Data / Model Comments: Lists the ‘Titles’ data set for viewing and editing. These comment have no visual impact within the interface merely act as text labels within the data file. Little used feature of limited use included for backwards compatibility.

Data / Model Graphics: Opens the model graphical edit display. Existing individual graphical elements can be viewed and edited through this display. New graphical elements should be added through the ‘Graphics / Add Graphics’ menus.

Data / Model Control Elements: Opens the model control elements edit display. Existing individual control elements can be viewed and edited through this display. New control elements should be added through the ‘Edit / Add Spacer to model’ menu.

Data / Compliance Data / Bush Properties (All): Opens the Bush data display section. All joints can be edited from this display both in terms of their kinematic coordinates and their compliant properties. The compliant bush properties include the definition of the bush’s local coordinate system as well as the bush stiffness properties.

Data / Compliance Data / Bush Properties (Stiffness): Opens the bush stiffness display window. It consists of a series of sliders that allows the selected bushes individual stiffness properties to be changed via sliders updating both the calculations and the displayed images simultaneously.

Data / Compliance Data / Spring Properties: Lists the ‘Spring’ data set for viewing and editing. The spring properties control the spring force applied to the compliant model through defining the free length, fitted length and linear rate. Note that the visual appearance of the spring is set under the Graphics / Enhanced Sizes section.

Data / Compliance Data / Damper Properties: Lists the ‘Damper’ data values for viewing and editing. This lists the Damper rate used for the front and rear dampers. Note that damper1 would be that normally used for the single damper in a corner model. Damper2 would be that used either for a second damper in a corner model or the damper for the second corner in a full axle model. Note that Individual damper properties can be altered by selecting them via the 3d view whilst in edit mode.

{bmc bm172.bmp}
Damper Properties

Data / Compliance Data / Tyre Properties…: Lists the ‘Tyres’ data set for viewing and editing. This lists the rolling radius for the front and rear axles, together with the width. The tyre width value is purely for graphical visualization, it does not alter the analysis results, also given is the tyre vertical stiffness values.

Data / Compliance Data / External Forces…: Opens the external force display window. This enables all external force data sets to be edited. Properties include magnitude, part attachment, orientation by ‘head’ and ‘tail’ definition and each force/sets on/off setting.

Data / Compliance Data / Roll Bar Properties…: Lists the roll bar properties for front and rear suspensions, used in the compliant model if a roll bar has been included. Properties are for the roll bar rate in terms of N.mm/Rad.

Data / Compliance Data / Linear Rack Properties…: Lists the properties for the rack bush lateral stiffness. This value is applied to the model at the bush(s) identified by the template as the ‘Rack Lateral Bush’.

{bmc bm173.bmp}
Linear Rack Bush Properties

Data / Compliance Data / Non-Linear Rack Properties…: Opens the display for the non-linear rack axial stiffness properties. If defined the non-linear rack stiffness replaces the Linear rack stiffness property identified in the preceding menu. It is an optional compliant data variable. Its definition is by a spline of displacement against force. The inclusion of the non-linear rack property causes the solver to perform an additional iterative step that identifies the rack axial force and applies a corrective force to achieve the correct rack axial displacement.

Data / Compliance Data / Bump Stop Properties…: Lists the optional properties for the Bump stops. Positions 1 and 2 are given for full axle models. For a single corner model normally only BumpStop1 is used. The properties of the bump stop are Force against displacement. Displacement is from the static position and is based on the motion of the Spring1 points. The force of the bump stop would usually be zero until some point in the +ve displacement is reached. The solver uses this curve to also derive the local bump stop stiffness for optional inclusion into the model stiffness matrix when solving compliantly.

{bmc bm174.bmp}
Bump Stop Properties

Data / Compliance Data / Drive Shaft Torque’s…: Lists the optional properties for the drive shaft Torque’s. This is only relevant if the drive shaft elements have been added to the model. The torque values are applied to the inboard ends of the drive shafts. The sign convention is based on the right hand grip rule, with the axis direction taken from the inboard point to the inboard joint center.

Data / Compliance Data / Drive Shaft Losses…: Lists the optional properties for the drive shaft Losses. This is only relevant if the drive shaft elements have been added to the model. Losses are given as a table of % loss against joint angle. Separate tables are given for the inner and outer joints. These loss tables are used by the solver to factor the calculated torque’s down by the relevant loss values.

Data / Compliance Data / Drive Shaft Properties…: Lists individual data variables associated with the drive shafts. Currently only lists the ‘Radius’ of the drive shaft joint. This is used to calculate the amount of cross car travel of the rollers associated with the inner drive shaft joint.

Data / Compliance Data / General Data…: Displays the values used for default stiffness’. The first is the singularity stiffness required by the solver for parts such as tie rods that mathematically have a degree of freedom, and secondly the stiffness used for ‘rigid’ ball joint. Mathematically the ball joints are not treated as rigid but bushes with very high stiffness in all three translation directions.

Data / Mass Data / C of G Properties: Displays the defined Mass properties of the current model. The mass properties specify the C of G values for each part in terms of magnitude, position and orientation. Its layout/requirements are similar to those used for the definition of bush stiffnesses. 

Data / Coordinates / Local Coordinate Systems: Opens the local coordinate system data display. This allows users to add, modify and delete local coordinate systems. These local coordinate systems can be used to define suspension hard points. Definition of the local system is by an origin, local axis and local plane. Options are given to provide alternative methods of defining these three items. Local axes systems can be visible on the graphical display and are ‘editable’ and ‘dragable’ through the graphical display. Hard points can be switched to use this local system by editing the hard point and selecting the required coordinate system. The hard points coordinates are automatically re-calculated in the new coordinate system to retain the same global position.

Data / Coordinates / Save: Saves the current suspension hard points to a temporary store, given a unique label for possible later retrieval. This temporary store only exists whilst the application is open such that all saved coordinate sets are lost when the application is closed. Any number of sets can be stored.

Data / Coordinates / Recall Saved: Recalls a saved hard point sets, replacing the current values with those in the temporary store. Saved sets identified by their label.

Data / Coordinates / Delete Saved: Deletes a saved hard points set from the temporary store. Only valid use is the simplifying of the displayed options through reduced menu list.

Data / Coordinates / Delete All: Deletes all saved hard point sets from the temporary store. Quicker than deleting one at a time if looking to start the storing from scratch.

Data / Set Static Angles…: Opens a simple data entry window that allows the user to set the static camber and toe angles directly. By defining the angles the stub axle points position is modified to obtain the required angles. The co-ordinates of the wheel centre are left unaltered.

Data / Use Extended Bump Travel: Enables the extended bump/rebound travel option. If unchecked the program solves at even increments of bump travel as specified by the increment value within the defined limits. When checked the solver runs through a specific prescribed list of bump positions. Note that -ve is rebound +ve is bump. The individual values are set through the following menu option.

Data / Edit Extended Bump Travel…: Opens a data list dialogue box to display/edit the extended bump travel data. These values are only used when the above option is checked. Each bump position can be given a label. This label is used within graph x-y listing for recognition by appearing on the status bar when 'hovering' over a plotted point.

Data / Use Extended Roll Travel: Enables the extended roll travel option. If unchecked the program solves at even increments of roll travel as specified by the increment value within the defined limits. When checked the solver runs through a specific prescribed list of roll angles. The individual values are set through the following menu option.

Data / Edit Extended Roll Travel…: Opens a data list dialogue box to display/edit the extended roll travel data. These values are only used when the above option is checked. Each roll position can be given a label. This label is used within graph x-y listing for recognition by appearing on the status bar when 'hovering' over a plotted point.

Data / Use Extended Steer Travel: Enables the extended steer travel option. If unchecked the program solves at even increments of steering travel as specified by the increment value within the defined limits. When checked the solver runs through a specific prescribed list of steer positions. The individual values are set through the following menu option.

Data / Edit Extended Steer Travel…: Opens a data list dialogue box to display/edit the extended steer travel data. These values are only used when the above option is checked. Each steer position can be given a label. This label is used within graph x-y listing for recognition by appearing on the status bar when 'hovering' over a plotted point.

Data / Use Extended Combined Motion Travel: Enables the extended combined motion travel option. If unchecked the program solves at even increments of bump travel and steering travel as specified by the associated increment value within their defined limits. This effectively equates to a the perimeter of a displacement box in bump and steering. When checked the solver runs through a specific prescribed list of bump, roll and steer positions. The individual values are set through the following menu option.

Data / Edit Extended Combined Motion Travel…: Opens a dialogue window for the display and editing of the extended combined bump/rebound, roll and steering envelope. This profile is used for identifying limits of ball joint articulations and future uses will include wheel envelopes.

Data / Component-Setup Toolbox…: Opens the component toolbox display. This utility allows users to build up a library of components for the current loaded model/template. Each component in the table has a defining dimension. Changing the selected option for each part updates all calculations and plotted graphs such that the impact of mixing ‘standard’ components can be instantly analyzed. The toolbox also has options to auto-adjust components to restore static toe, camber or castor values. The internal optimizer can be used to identify the best mix of defined components when compared to specified targets.

+$#>Pull Down Menu Items - Edit

Edit / Edit Menu Tree: Displays a tree based display list of the Edit commands. Such that users can optionally select actions from a menu tree rather the individual pull down menus. This menu tree also includes the Add Graphics menus.

Edit / Undo (Ctrl+Z): Edit undo provides a function that after a number of changes to the suspension hard points coordinates, it is possible to step back through the changes undoing them step by step. This menu can be used or often more conveniently by using the equivalent short cut key strokes Ctrl+Z. If this menu is not available then no edit events are left in the buffer to undo.

Edit / Redo (Ctrl+Y): provides a function that after a number of undo changes to the suspension hard points coordinates, it is possible to reapply the the changes that have been undone. This menu can be used or often more conveniently by using the equivalent short cut key strokes Ctrl+Y. If this menu is not available then no edit events are left in the buffer to redo.

Edit / Modify Mode: Sets the data edit mode as either Edit, Joggle or Drag. More normal to use equivalent convenience ‘File’ toolbar icons.

Edit / Change Mode: Sets the change mode as either ‘Change Part Lengths’, ‘Retain Part Lengths’ or ‘Set Part Lengths’. The default ‘change’ mode is to change the lengths and relationships between points on a part as a hard point is modified. The ‘Retain Part Lengths’ option restricts the pick-able points to just those that are connected to ‘ground’ but retains the defined part lengths as a point is modified. The ‘Set Part Lengths’ mode retains hard point positions and allows the user to modify a part by directly changing one or more length properties of the part. With the ‘Set Part Lengths’ mode pnt-pnt graphical elements become editable as do pnt to line graphical elements.

Edit / Symmetric Suspension: Switches the suspension type between symmetric and asymmetric. This affects both corner models and full axle models. When set to symmetric points that are identified as symmetric pairs by the template are kept symmetric when one of the pair is modified.

Edit / Point Coincidence Pick: Enables Point Coincidence checking. With Point Coincidence on, editing hard points checks for more than one hard point within the pick tolerance and presents a list for selection, including ‘All points’. Selecting all points creates an equivalent temporary group during any subsequent change.

Edit / All Settings (Ctrl+S): Opens a single display window that allows a single point of access to a large number of the graphical, graph and setup settings. This consolidated display supplements the existing individual menu structure to provide quicker overall control of the display.

Edit / Add to Model / Add Part / 2 Point Link: When in template builder mode adds a new part to the current template. The 2 Point Link is a simple part having two connection points, such as a track rod or tie rod.

Edit / Add to Model / Add Part / 3 Point Wishbone: When in template builder mode adds a new part to the current template. The 3 Point Wishbone is a simple part having three connection points, normally two to ground (or sub-frame) with the third being a ball joint.

Edit / Add to Model / Add Part / 4 Point Wishbone: When in template builder mode adds a new part to the current template. The 4 Point Wishbone is a simple part having four connection points, normally two inboard connected to ground (or sub-frame) with the outer two being ball joint connections to a hub/stub axle.

Edit / Add to Model / Add Part / 3 Point Stub Axle: When in template builder mode adds a new part to the current template. The 3 Point Stub Axle part has three connection points, normally these would be an upper and lower ball joint and a tie rod connection. This part also adds a wheel centre and stub axle point.

Edit / Add to Model / Add Part / 4 Point Stub Axle: When in template builder mode adds a new part to the current template. The 4 Point Stub Axle part has four connection points, normally these would be a combination of wishbone ball joints and a tie rod connections. This part also adds a wheel centre and stub axle point.

Edit / Add to Model / Add Part / 5 Point Stub Axle: When in template builder mode adds a new part to the current template. The 5 Point Stub Axle part has five connection points, normally these would be a combination of wishbone ball joints and a tie rod connections. This part also adds a wheel centre and stub axle point.

Edit / Add to Model / Add Part / 3 Point Strut: When in template builder mode adds a new part to the current template. The 3 Point Strut part has three connection points, normally these would be the strut top, lower ball joint and a tie rod. This part also adds the wheel centre, stub axle and slider points.

Edit / Add to Model / Add Part / 4 Point Strut: When in template builder mode adds a new part to the current template. The 4 Point Strut part has four connection points, normally these would be the strut top, and a combination of ball joints and a tie rods. This part also adds the wheel centre, stub axle and slider points.

Edit / Add to Model / Add Part / Add Damper: When in template builder mode adds a Damper to the current template. Technically the Damper is not a part but two points tagged to identify the damper upper and lower attachment points.

Edit / Add to Model / Add Part / Add Spring: When in template builder mode adds a Spring to the current template. Technically the Spring is not a part but two points tagged to identify the spring upper and lower attachment points.

Edit / Add to Model / Add Part / Add Spring-Damper: When in template builder mode adds a co-axial Spring-Damper to the current template. Technically the Spring-Damper is not a part but two points tagged to identify the spring-damper upper and lower attachment points.

Edit / Add to Model / Add Part / Add Bump Stop: When in template builder mode adds a Bump Stop to the current template. Technically the Bump Stop is not a part but two points tagged to identify the Bump Stop upper and lower attachment points.

Edit / Add to Model / Add Part / Add 3 Point SubFrame: When in template builder mode adds a part to the current template. The 3 point sub frame has three attachments points that would normally be connected to ground. Suspension links could then be attached to this sub frame rather than directly to ground.

Edit / Add to Model / Add Part / Add 4 Point SubFrame: When in template builder mode adds a part to the current template. The 4 point sub frame has four attachments points that would normally be connected to ground. Suspension links could then be attached to this sub frame rather than directly to ground.

Edit / Add to Model / Add Part / Semi Trailing Arm: When in template builder mode adds a part to the current template. The Semi Trailing Arm has two attachment points that would normally be connected to ground. This part also adds the wheel centre and stub axle points.

Edit / Add to Model / Add Part / Twist Beam: When in template builder mode adds two parts to the current template. The Twist Beam has two attachment points that would normally be connected to ground. This part also adds the wheel centre and stub axle points for both sides.

Edit / Add to Model / Add Part / 1 Part Rigid Axle: When in template builder mode adds a part to the current template. The 1 Part Rigid Axle has four attachment points that would normally be connected to tie rods. This part also adds the wheel centre and stub axle points for both sides.

Edit / Add to Model / Add Part / 2 Part Rigid Axle: When in template builder mode adds two parts to the current template. The 2 Part Rigid Axle has five attachment points that would normally be connected to tie rods. This part also adds the wheel centre and stub axle points for both sides.

Edit / Add to Model / Add Point / to Ground, Abs Position…: Adds a new point to the current template. If both front and rear ends are in the model and displayed the user is prompted to identify to which end the point should be added. A new point is added to the template and attached to the ground. The user is then presented with the current properties for editing.

Edit / Add Point / to Ground, Rel to Point Pos (Cartesian) Adds a new point to the current template. If both front and rear ends are in the model and displayed the user is prompted to identify to which end the point should be added. Only the points associated with the ground are made visible for suitable selection. The user must select a point on the part relative to which the new point is defined in Cartesian coordinates.

Edit / Add Point / to Ground, Rel to Point Pos (Spherical) Adds a new point to the current template. If both front and rear ends are in the model and displayed the user is prompted to identify to which end the point should be added. Only the points associated with the ground are made visible for suitable selection. The user must select a point on the part relative to which the new point is defined in Spherical coordinates.

Edit / Add Point / to Ground, Rel to Point Pos (Cylindrical) Adds a new point to the current template. If both front and rear ends are in the model and displayed the user is prompted to identify to which end the point should be added. Only the points associated with the ground are made visible for suitable selection. The user must select a point on the part relative to which the new point is defined in Cylindrical coordinates.

Edit / Add Point / to Ground, Between Points Adds a new point to the current template. If both front and rear ends are in the model and displayed the user is prompted to identify to which end the point should be added. Only the points associated with the ground are made visible for suitable selection. The user must select two points on the part between which is added the new point.

Edit / Add Point / to Part, Abs Position…: Adds a new point to the selected part. On selection of this menu the Part labels and notional centres are made visible for suitable selection. Once selected a point is added at the user defined absolute position.

Edit / Add Point / to Part, Rel to Point Pos. (Cartesian): Adds a new point to the selected part. On selection of this menu the Part labels and notional centres are made visible for suitable selection. Once a part has been selected only this part is made visible and the user must select a point on the part relative to which the new point is defined in Cartesian coordinates.

Edit / Add Point / to Part, Rel to Point Pos. (Spherical): Adds a new point to the selected part. On selection of this menu the Part labels and notional centres are made visible for suitable selection. Once a part has been selected only this part is made visible and the user must select a point on the part relative to which the new point is defined in Spherical coordinates.

Edit / Add Point / to Part, Rel to Point Pos. (Cylindrical): Adds a new point to the selected part. On selection of this menu the Part labels and notional centres are made visible for suitable selection. Once a part has been selected only this part is made visible and the user must select a point on the part relative to which the new point is defined in Cylindrical coordinates.

Edit / Add Point / to Part, Between Points…: Adds a new point to the selected part. On selection of this menu the Part labels and notional centres are made visible for suitable selection. Once a part has been selected only this part is made visible and the user must select two points on the part between which is added the new point.

Edit / Add Point / to Graphical Element (Pick) Adds a new point to the template who’s position is based on the selected graphical element. Graphical elements can have one or more ‘hit’ point such as sphere centre which can be selected. Use the ‘hover over’ functionality to indicate the graphical element that will be selected.

Edit / Add Point / Calculated Point…: Adds a new ‘calculated’ point to the current template. These calculated points are a series of pre-defined positional points that can be optional included in the template. The different points range from the Tyre Contact Point (TCP) through to the damper normal. These calculated points whilst their position can’t be edited (as they are calculated points), they can be set as visible and used in the drawing of graphics and in user defined SDF’s. A brief description of each is given below:

TCP – The tyre contact point, the point on the ‘rigid’ tyre disc in contact with the ground plane.
Castored TCP, The position that the original ‘static’ TCP point moves to under the prescribed articulation.
Steer Axis (Virtual) upper, An upper point placed on the derived steering axis. Together with the equivalent lower axis point this can be used to graphically show the virtual steering axis.
Steer Axis (Virtual) lower, A lower point placed on the derived steering axis. Together with the equivalent upper axis point this can be used to graphically show the virtual steering axis.
KPI Normal, The intersection point on the kingpin axis from the normal to the spindle axis.
Castor Intersect, The intersection point of the castor axis and the ground plane.
Spindle Normal, The intersection point on the spindle axis from the normal to the steering axis.
Spindle/Damper Normal, The intersection point on the spindle axis from the normal to the damper axis.
Damper Normal, The intersection point on the damper axis from the normal to the spindle axis.

Edit / Add to Model / Spring 1 (pick two points): Provides an interactive ‘picking’ method of adding a spring to the current model. It requires the user to pick the two spring end points, the order being the end attached to the body followed by the end attached to the suspension. Thus it requires the required point positions to already exist in the model, (use Add Point / to Part and Add Point / to Ground menu options to do this if they don’t already exist). This can also be performed by directly editing the template via the template editor. This ‘Add’ changes not only the model but also the underlying template. Thus if the change is to be retained the template must also be saved. Note that if the Spring 1 already exists in the current template you cannot add it again. You must delete it first or change the point association via the template editor.

Edit / Add to Model / Spring 2 (pick two points): Provides an interactive ‘picking’ method of adding a spring to the current model. It requires the user to pick the two spring end points, the order being the end attached to the body followed by the end attached to the suspension. Thus it requires the required point positions to already exist in the model, (use Add Point / to Part and Add Point / to Ground menu options to do this if they don’t already exist). This can also be performed by directly editing the template via the template editor. This ‘Add’ changes not only the model but also the underlying template. Thus if the change is to be retained the template must also be saved. Note that if the Spring 2 already exists in the current template you cannot add it again. You must delete it first or change the point association via the template editor.

Edit / Add to Model / Damper 1 (pick two points): Provides an interactive ‘picking’ method of adding a damper to the current model. It requires the user to pick the two damper end points, the order being the end attached to the body followed by the end attached to the suspension. Thus it requires the required point positions to already exist in the model, (use Add Point / to Part and Add Point / to Ground menu options to do this if they don’t already exist). This can also be performed by directly editing the template via the template editor. This ‘Add’ changes not only the model but also the underlying template. Thus if the change is to be retained the template must also be saved. Note that if the Damper 1 already exists in the current template you cannot add it again. You must delete it first or change the point association via the template editor.

Edit / Add to Model / Damper 2 (pick two points): Provides an interactive ‘picking’ method of adding a damper to the current model. It requires the user to pick the two damper end points, the order being the end attached to the body followed by the end attached to the suspension. Thus it requires the required point positions to already exist in the model, (use Add Point / to Part and Add Point / to Ground menu options to do this if they don’t already exist). This can also be performed by directly editing the template via the template editor. This ‘Add’ changes not only the model but also the underlying template. Thus if the change is to be retained the template must also be saved. Note that if the Damper 2 already exists in the current template you cannot add it again. You must delete it first or change the point association via the template editor.

Edit / Add to Model / BumpStop 1 (pick two points): Provides an interactive ‘picking’ method of adding a bump stop to the current model. It requires the user to pick the two bump stop end points, the order being the end attached to the body followed by the end attached to the suspension. Thus it requires the required point positions to already exist in the model, (use Add Point / to Part and Add Point / to Ground menu options to do this if they don’t already exist). This can also be performed by directly editing the template via the template editor. This ‘Add’ changes not only the model but also the underlying template. Thus if the change is to be retained the template must also be saved. Note that if the BumpStop 1 already exists in the current template you cannot add it again. You must delete it first or change the point association via the template editor. Its properties are set via the Bump Stop data menu.

Edit / Add to Model / BumpStop 2 (pick two points): Provides an interactive ‘picking’ method of adding a bump stop to the current model. It requires the user to pick the two bump stop end points, the order being the end attached to the body followed by the end attached to the suspension. Thus it requires the required point positions to already exist in the model, (use Add Point / to Part and Add Point / to Ground menu options to do this if they don’t already exist). This can also be performed by directly editing the template via the template editor. This ‘Add’ changes not only the model but also the underlying template. Thus if the change is to be retained the template must also be saved. Note that if the BumpStop 2 already exists in the current template you cannot add it again. You must delete it first or change the point association via the template editor. Its properties are set via the Bump Stop data menu.

Edit / Add to Model / Two Part Rack: This function provides a simple single click method of adding a two-part compliant rack to the template. It can only be applied to a full axle model, as it needs both steering attachment points to have already been defined in the template. This option adds two parts, (the rack cross-link and the rack bush), six new points, (including both connection points and C of G points), four new bushes and associated graphic elements. To retain this modified template either save it with the model file or as a user or custom template.

Edit / Add to Model / Roll Bar (pick part): This function provides a simple method of adding a roll-bar to the current models template. It can only be applied to a full axle model, as it needs to connect to both suspension sides. The type of roll–bar it adds uses two points to ground and drop links from the bar ends to the suspension part. Thus the user must pick the attachment part and define a point on this part for the drop link to attach to. You do not pre-define this connecting point but enter its global position as part of the ‘Add Roll Bar’ function, (it is automatically mirrored across to the other side). This function adds three new parts, ten new points, seven new bushes and associated graphics. The reason for the odd number of bushes is because the roll bar stiffness is defined through a revolute bush placed such that it joins the two halves of the roll bar. To retain this modified template either save it with the model file or as a user or custom template.

Edit / Add to Model / Roll Bar (pick point): This function is similar to that above in that it provides a simple method of adding a roll-bar to the current models template. It can only be applied to a full axle model, as it needs to connect to both suspension sides. The type of roll–bar it adds uses two points to ground and drop links from the bar ends to the suspension part. Thus the user must pick the attachment point for the drop link to attach to. (the attachment is automatically mirrored across to the other side via the symmetric point function). This function adds three new parts, eight new points, seven new bushes and associated graphics. The reason for the odd number of bushes is because the roll bar stiffness is defined through a revolute bush placed such that it joins the two halves of the roll bar. To retain this modified template either save it with the model file or as a user or custom template.

Edit / Add to Model / Compliant Hub(s): This function provides a simple single click method of adding a compliant hub element to the template. This existing upright part is detected and replaced by two parts, the upright and the hub. A compliant bush is placed between the two and tagged such that in compliant mode it picks up the default ‘rigid’ stiffness unless specifically defined by the user.

Edit / Add to Model / Drive Shaft(s): This function provides a simple single click method of adding the drive shaft geometry to the template. It does not add parts and joints to the model only graphical points to represent the drive shaft joint geometry. This drive shaft geometry is then used to calculate the forces and torque’s applied to the upright due to the supplied input drive torques. Two drive shaft types are available a fixed length drive shaft where the inner joint accommodates the ‘plunge’ or a vary length drive shaft where the shaft is assumed to be two part with its own splined sliding joint.

Edit / Add to Model / SubFrame Part (pick Points): This function provides a method to modify the current template by adding a subframe part. This part is connected to ground at the selected existing ground points. Individual points are then selected to switch from being connected to ground to connected to this new subframe part.

Edit / Add to Model / Length Actuator: Provides an interactive ‘picking’ method of adding a specific control component to the model. The Length actuator combines a distance sensing change input with a change in length setting output. The input distance is set as the incremental distance between two points. On add, by default this is set to the spring1 points, but can be post edited by the user. The user is required to pick the two points for which the length is controlled by the actuator. The two points must be different but on the same part. The relationship of sensor displacement and change in picked length is based on a user editable look-up table. Each length actuator has its own look-up table. The application of these length actuators is based on a one step delay, this is because with a directly coupled solve the kinematic solutions will tend not to converge due to the coupled nature. To edit the properties of an actuator, ensure visible via ‘Solver’ option and then when in edit mode pick the actuator required to edit. Its graphical properties are displayed with the look-up table being editable via a further icon selection.

Edit / Add to Model / Position Actuator: Provides an interactive ‘picking’ method of adding a specific control component to the model. Similar to the Length actuator above it combines a distance sensing change input with a change in position setting output. The input distance is set as the incremental distance between two points. On add, by default this is set to the spring1 points, but can be post edited by the user. The user is required to pick a point for which the position is controlled by the actuator. A user defined global vector passing through the picked point defines the position change. The point must be attached to ground. The relationship of sensor displacement and change in picked position is based on a user editable look-up table. Each actuator has its own look-up table. The application of these position actuators is based on a one step delay, this is because with a directly coupled solve the kinematic solutions will tend not to converge due to the coupled nature. To edit the properties of an actuator, ensure visible via ‘Solver’ option and then when in edit mode pick the actuator required to edit. Its graphical properties are displayed with the look-up table being editable via a further icon selection.

Edit / Add to Model / Part C of Gs / to Part, Abs Pos: Provides an interactive means by which a parts C of G may be added to the model, (this can also be done directly through the template editor). The user must identify which part the C of G point is to be applied to by picking from the now visible part labels. The user then specifies its actual location in absolute global co-ordinates.

Edit / Add to Model / Part C of Gs / to Part, Rel to Point Pos: Provides an interactive means by which a parts C of G may be added to the model, (this can also be done directly through the template editor). The user must identify which part the C of G point is to be applied to by picking from the now visible part labels. To define its location the user must then pick a point on this part and specify its location relative to the selected point.

Edit / Add to Model / Part C of Gs / to Part, Between Points: Provides an interactive means by which a parts C of G may be added to the model, (this can also be done directly through the template editor). The user must identify which part the C of G point is to be applied to by picking from the now visible part labels. To define its location the user must then pick two points on this part the C of G is then positioned midway between these selected points.

Edit / Add to Model / Steering Effort Points + Force Set: Provides a simple single click method of adding a set of points to the steerable hub that can be used for attaching a force set that moves with the steered hub. This menu includes the creation of this new force set, added after the last of the currently defined force sets. The points are defined in a local coordinate system that is also added as part of this menu action.

Edit / Delete from Model / Part: In template builder mode allows for parts and associated points to be deleted from the current template through on screen picking.

Edit / Delete from Model / Point: In template builder mode allows for points and associated graphical elements to be deleted from the current template through on screen picking.

Edit / Delete from Model / Graphic or Measure: In template builder mode allows for graphical and measure elements to be deleted from the current template through on screen picking.

Edit / Delete from Model / Spring 1: Provides a convenience function that automatically removes the spring 1 definition from the current selected models template. Note that the spring 1 element tags two end points as being associated with the spring. On deletion of the spring 1 element the two points remain defined in the model template.

Edit / Delete from Model / Spring 2: Provides a convenience function that automatically removes the spring 2 definition from the current selected models template. Note that the spring 2 element tags two end points as being associated with the spring. On deletion of the spring 2 element the two points remain defined in the model template.

Edit / Delete from Model / Damper 1: Provides a convenience function that automatically removes the damper 1 definition from the current selected models template. Note that the damper 1 element tags two end points as being associated with the damper. On deletion of the damper 1 element the two points remain defined in the model template.

Edit / Delete from Model / Damper 2: Provides a convenience function that automatically removes the damper 2 definition from the current selected models template. Note that the damper 2 element tags two end points as being associated with the damper. On deletion of the damper 2 element the two points remain defined in the model template.

Edit / Delete from Model / BumpStop 1: Provides a convenience function that automatically removes the bumpstop 1 definition from the current selected models template. Note that the bumpstop 1 element tags two end points as being associated with the bump stop. On deletion of the bumpstop 1 element the two points remain defined in the model template.

Edit / Delete from Model / BumpStop 2: Provides a convenience function that automatically removes the bumpstop 2 definition from the current selected models template. Note that the bumpstop 2 element tags two end points as being associated with the bump stop. On deletion of the bumpstop 2 element the two points remain defined in the model template.

Edit / Delete from Model / Two Part Rack: Provides a convenience function that automatically removes the Two Part Rack parts and points from the current selected models template.

Edit / Delete from Model / Roll Bar: Provides a convenience function that automatically removes the Roll Bar parts and points from the current selected models template.

Edit / Delete from Model / Compliant Hub(s): Provides a convenience function that automatically removes the Compliant Hub(s) parts and points from the current selected models template.

Edit / Delete from Model / Drive Shaft(s): Provides a convenience function that automatically removes the Drive Shaft(s) parts and points from the current selected models template.

Edit / Convert Corner to Axle Model: In some instances even for an independent suspension it is required to model a complete axle rather than a corner model. This may be because it is required to include a compliant rack, anti roll-bar, sub-frame or any connecting part. This can either be done by hand through the template editor or by using this convenience function. This single click operation will review the current template and then add the necessary parts, point, connections and graphics to produce a full axle template. To retain this modified template either save it with the model file or as a user or custom template.

Edit / Add Spacer to Model: This function provides a simple ‘pick to add’ method of adding a spacer to the template. Spacers can either be between two parts or between a part and ground. Spacers are added with properties of length and orientation. The orientation being defined by a global vector. Spacers can then be modified in the usual ways, edit drag, joggle etc. They can also be added to the component toolbox as a variable property part.

Edit / Mesh Rigid Part: This ‘ meshing’ utility allows the user to split a single part into a series of smaller sub-parts to provide a technique for including component flexibility’s.

Edit / Convert Ball Joint to Slot: This utility allows the user to convert a simple ball joint such as the outer track rod into a slotted joint. The slotted joint is effectively a special case of a universal joint. A special case in that one of the points defining the 2nd axis lies on the line of the 1st axis. This utility modifies the template by the addition of a part to represent the ‘spider’ of the joint and makes connections between this part and the two original connecting parts. The orientation of the slot is controlled by the ‘normal’ axis marker point.

Edit / Merge Spring1 > Damper1: This simple function conveniently merges the point definitions of spring 1 and damper 1. In this case the Spring 1 points are changed to be the same as Damper1’s. In addition if the Spring 1 points are no longer referenced by another other special element or solver they are removed from the template.

Edit / Merge Damper1 > Spring1: This simple function conveniently merges the point definitions of spring 1 and damper 1. In this case the Damper 1 points are changed to be the same as Spring1’s. In addition if the Damper 1 points are no longer referenced by another other special element or solver they are removed from the template.

Edit / Merge Spring2 > Damper2: This simple function conveniently merges the point definitions of spring 2 and damper 2. In this case the Spring 2 points are changed to be the same as Damper2’s. In addition if the Spring 2 points are no longer referenced by another other special element or solver they are removed from the template.

Edit / Merge Damper2 > Spring2: This simple function conveniently merges the point definitions of spring 2 and damper 2. In this case the Damper 2 points are changed to be the same as Spring2’s. In addition if the Damper 2 points are no longer referenced by another other special element or solver they are removed from the template.

Edit / Convert Damper1 to Parts: This simple function converts the Damper 1 to parts. Two parts are added to represent the upper and lower portions of the damper. Local coordinate axes systems are added to define the associated points and mimic the behavior of a slider.

Edit / Convert Damper2 to Parts: This simple function converts the Damper 2 to parts. Two parts are added to represent the upper and lower portions of the damper. Local coordinate axes systems are added to define the associated points and mimic the behavior of a slider.

Edit / Set Ride Height - Bump: A utility function that will reset the vehicle model to a new ride height by simple change in the bump height. The value required is a delta from the current position. A positive value lowers the body, i.e. reduces the ride height.

Edit / Set Ride Height – Bump + Pitch: A utility function that will reset the vehicle model to a new ride height by a combination of bump height change and pitch angle. The values required are the deltas from the current position. A positive bump value lowers the body, i.e. reduces the ride height and a positive pitch angle rotates towards the rear. For a full vehicle model the pitch rotation is about the front wheel center axis. For a single end model the pitch is rotation about the modeled suspension end.

Edit / Set Ride Height – Adjust Springs: A utility function that will reset the vehicle spring fitted lengths such that the spring forces balance the defined unsprung weight split. This results in no change in ride height, just changes to the relevant spring fitted length(s). The user must provide values for the unsprung mass and the percentage of the unsprung weight on the front axle.

Edit / Set Ride Height – Match to Springs: A utility function that will reset the vehicle ride height such that the spring forces balance the defined unsprung weight split. This results a both bump and pitch changes in ride position, (only pitch if full vehicle model). The relevant spring fitted length(s) are also changed. The user must provide values for the unsprung mass and the percentage of the unsprung weight on the front axle. This allows the user to have spring properties dictate the ride height position.

Edit / Set Ride Height – Match to Weight Change: A utility function that will reset the vehicle ride height based on a change in vehicle unsprung weights. It is not assumed that the initial vehicle ride position balances the current spring settings, (this can be checked/set first using one of the two options above), but effects the change in ride position based purely on the difference between the two defined weight conditions.

Edit / Groups / Current: Makes a previously created points group the current group. Groups are identified by their unique label from the menu list. Groups limit edit functions to just hard points that are members of the group. Edited points then move as a group, i.e. same translation applied to all.

Edit / Groups / Cancel: Cancels the current group selection, returning back to all hard points accessible for individual editing.

Edit / Groups / Delete: Deletes the selected group. This does not delete any points from the model, (as you can’t do this at any level other than template editing), merely removes the group association. Groups are identified by their unique label from the menu list.

Edit / Groups / Create…: Creates an new points group. A new group must be given a unique label to identify it. The number of points required to add to it set and each required point picked from the available suspension end lists.

Edit / Groups / Pick Temporary…: Creates an new temporary points group . The points are added to this group by selecting a displayed screen region. All visible points within the region being added to it. Unlike the conventional groups this does not need to have a label nor does it need to be ‘made current’, once the points have been picked it will automatically be set to current.  Temporary groups are not saved and when made non-current using the ‘delete’ option they are lost and would need to be re-created.

Edit / Groups / Edit: Provides an editing option to existing point groups. The points in the group can be changed, added to or removed from. Groups are identified by their unique label from the menu list.

+$#>Pull Down Menu Items - View

View / Refresh: Updates all graphical displays, both Graphics and Graphs.

View / Dynamic Viewing: Menu option to switch between dynamic viewing and edit modes. Either by a toggle action or by specific selection..

View / Translate View: Sets the dynamic view mode to translate. If currently in edit mode this will also cause a change to the dynamic view mode. Translation by left mouse button hold and move.

View / Scale View: Sets the dynamic view mode to scale. If currently in edit mode this will also cause a change to the dynamic view mode. Scale by left mouse button hold and drag vertically.

View / Rotate View: Sets the dynamic view mode to rotate. If currently in edit mode this will also cause a change to the dynamic view mode. Rotation by left mouse button hold and move.

View / Pick View Centre: Allows the view centre to be picked. The pick is based on the nearest picked hard point. The current view is translated such that picked point becomes the view centre, no change is made to either the scale or orientation of the view. Subsequent view rotations will be about this new ‘object’ point. 

View / Zoom: Pick the area of the display to zoom to fit current window. The zoom function can accommodate either a two press approach to area selection or a single press, hold and drag selection, a simple time delay trap being used to identify which type is being used. The zoomed view will retain the correct aspect ratio, (i.e. no distortion is allowed), and thus the final displayed region will include additional regions at either the top and bottom or both sides.

View / Autoscale (Ctrl+A): Resets the graphical view such that all drawn components appear within the display window. Note that this is only applied to the graphics window and not the graphs.

View / Fill Style: Sets the fill style to be used in the graphics display. Not all the fill style options are supported by every machine. Two graphics frame driver options are used one of which will not correctly support two of the fill styles. The fill styles available are, Wire Frame, Filled, Hidden Line and Depth Buffered (flat shaded). The later two will not work correctly unless the graphics frame type has been set to OpenGL

View / Std Views: Three orthogonal views are offered to aid simple planar viewing of the 3D model. The std views are y-z (front view), z-x (side view) and x-y (top view). Equivalent view toolbar icons are also available. An additional ISO view is available, this does not have an equivalent toolbar icon.

View / Saved Views / Save…: Saves the current 3D view settings to a temporary store, given a unique label for possible later retrieval. This temporary store only exists whilst the application is open such that all saved views are lost when the application is closed. Any number of views can be stored.

View / Saved Views / Recall Saved: Recalls a saved view, replacing the current view with that in the temporary store. Saved views are identified by their labels.

View / Saved Views / Delete Saved: Deletes a saved view from the temporary store. Only valid use is the simplifying of the displayed options through reduced menu list.

View / Saved Views / Delete All: Deletes all saved views from the temporary store. Quicker than deleting one at a time if looking to start the storing from scratch.

View / Set Display Mode Tool…: Opens the display mode tool. This provides a single dialogue box that can be used to control all 3d view display modes. The four available display modes are;

	Articulation Display
	Deformed Geometry  (compliance mode only)
	Mode Shape  (compliance mode only)
	Forced-Damped  (compliance mode only)

Each of the four display modes can be animated. The speed of animation since the introduction of segments requires a speed of refresh value. This can be edited directly via the relevant menu or changed via the slider given on the ‘Display Mode Tool’ just beneath the animate icon.

The articulation display can be set as one of the following;

	Full + Half + Static (normal articulation displacement display)
	Full + Static (normal articulation displacement display)
	Static Only (normal articulation displacement display)
	All Steps (normal articulation displacement display)
            Single Step (define which step from current articulation list)

{bmc bm175.bmp}
The Display Mode Tool.

The compliant deformed geometry is shown for a specified articulation position and for a defined scaler. This scaler is applied to the actual compliant displacements to enable small displacements to be visualized.

The compliant Mode Shape display is for a selected mode. The modes are identified by number rather than by frequency, (although the frequency value is shown on the 3d view). A scaler is also applied to modal displays to enable small modal displacements to be visualized.

The Forced-Damped display shown for a specified frequency. A scaler is applied to the amplitudes to enable small displacements to be visualized.

As an alternative to using the display mode tool, individual menus can be used to set the display mode and associated properties.

View / Screen Display / Full+Half+Static: Sets the display mode to ‘Articulation Display’ and will show the suspension at full travel, mid travel and static. The ‘travel’ will be bump/rebound, roll or steer as appropriate to the current analysis mode.

View / Screen Display / Full+Static: Sets the display mode to ‘Articulation Display’ and will show the suspension at full travel and static. The ‘travel’ will be bump/rebound, roll or steer as appropriate to the current analysis mode.

View / Screen Display / Static Only: Sets the display mode to ‘Articulation Display’ and will show the suspension at static position only.

View / Screen Display / All Steps: Sets the display mode to ‘Articulation Display’ and will show the suspension at all calculated travel points. The ‘travel’ will be bump/rebound, roll or steer as appropriate to the current analysis mode.

View / Screen Display / Single Step: Sets the display mode to ‘Articulation Display’ and will show the suspension at a specified single travel step. The ‘travel’ will be bump/rebound, roll or steer as appropriate to the current analysis mode. A number greater than the actual available steps will be clipped to the limiting value.

View / Screen Display / Deformed Geometry: Sets the display mode to ‘ Deformed Geometry’  showing the suspensions compliant deformation at a specified single travel step. The currently specified scaling factor will be applied to all displacements.

View / Screen Display / Mode Shape: Sets the display mode to ‘Mode Shape’ showing the suspensions modal shape for the static position for the currently specified mode number. The currently specified scaling factor will be applied to all modal displacements.

View / Screen Display / Forced-Damped: Sets the display mode to ‘Forced-Damped’ showing the suspensions forced response for the static position for the currently specified frequency. The defined scaling factor will be applied to all amplitudes.

View / Animate (On/Off): Switches on animation of the suspension(s) for the currently defined display mode. All standard viewing and editing functions can still be used whilst the animation is on. The actual display mode, position, articulation type etc are controlled through other menu settings, (see above).

View / Free Body Diagram: Changes the graphical display to just show the points, forces and graphical elements associated with a single part. The selection menu allows the user to pick for the selected corner any available part.

View / Definition Values: A utility is available that allows the user to graphically modify the model through basic angles and offsets. This menu option switches the visibility of the ‘Definition Values’ which when in an orthogonal view indicate main angles (i.e. Camber Castor) and offsets. These can be edited, joggles or dragged in the same way as conventional hard points, leading to an alternative method of rapidly defining model points.

View / SetUp Definition Values: The ‘Definition Values’ utility can be structured by the user to vary how the methods are applied. In particular which points remain fixed and which are modified to meet the defined angles/offsets.

+$#>Pull Down Menu Items - Tracking

Tracking / Toggle: Not strictly a toggle, but a cycle through the available tracking options. The available tracking options change depending whether the current view is orthogonal or not.

Tracking / All: Only applicable if in an orthogonal view. ‘All’ actually means two axis, i.e. all axes in the current orthogonal view.

Tracking / X: Changes the tracking direction to the x-axis. If the selection is not valid, for instance if in the y-z orthogonal view, then this selection is ignored.

Tracking / Y: Changes the tracking direction to the y-axis. If the selection is not valid, for instance if in the x-z orthogonal view, then this selection is ignored.

Tracking / Z: Changes the tracking direction to the z-axis. If the selection is not valid, for instance if in the x-y orthogonal view, then this selection is ignored.

Tracking / User Vector: Changes the tracking direction to the user defined vector. The user vector is defined elsewhere either through point picking or by directly editing the vector values.

Tracking / Include User Vector on Cycle: When checked, the user vector will be included in the cycling through the tracking direction options, i.e. All, X, Y, Z, (User), All, X….

Tracking / Edit User Vector: Direct editing of the user vector direction. Based on three components, X Y and Z.

Tracking / Pick User Vector: The user vector will be defined by a current graphical line direction. Picking of the required line sets the user vector components. If the following option is set as this graphical line is changed (through model modifications) the user vector is similarly changed.

Tracking / Lock to Picked User Vector: When checked the user vector when picked will be locked to the picked vector, such that if the model hard point positions are altered and the picked vector direction changes then the user vector will be changed to this new orientation.

Tracking / Tracking Style / Linear (default): The original (and thus default) method used for tracking was along one (or more ) linear directions. When this option is checked a point will track along a linear direction (or possibly within a 2-D plane when using the ‘All’ option). Other tracking options have been added, see below.

Tracking / Tracking Style / Spherical: The spherical tracking style will modify the points position when dragged such that it will be put back on to the surface of a user specified sphere. The sphere being set by a previously selected centre point and the sphere radius being the original distance of the modified point from the sphere centre. This modification of the points position after it has been dragged means that whilst the tracking direction might be set to just one axis (i.e. Z) it could be modified in the other two directions when put back on to the sphere’s surface.

Tracking / Tracking Style / Circular: The circular tracking style will modify the points position when dragged such that it will be put on the arc of a user specified 3d circle. The circle being set by a previously selected centre point and point in the plan of the circle. This modification of the points position after it has been dragged means that whilst the tracking direction might be set to just one axis (i.e. Z) it could be modified in the other two directions when put back on to the sphere’s surface.

Tracking / Pick Spherical Tracking Centre: Single screen pick of the centre of the tracking sphere for future use of the spherical tracking style.

Tracking / Pick Circular Tracking Centre and Plane: Two point screen picks of the centre of the tracking circle and a point in the plane of the circle, for future use of the circular tracking style.

Tracking / Visible: Sets the visibility of the tracking lines. Note that tracking lines are only visible when in dynamic view mode.

Tracking / Length: Tracking lines are drawn on the display to a fixed length. The size of this graphical length can be changed from the default value through the opened edit box.

+$#>Pull Down Menu Items - Graphics

Graphics / Graphics Switches Menu Tree: Toggles the visibility of a tree structure dialogue box that includes the menus for all graphics settings. Provides an alternative method for users to control graphics visibility’s without having to use the individual pull down menu entries.

Graphics / Point Short Labels: Toggles the visibility of the template short labels on the graphical display. The size and colour is user definable. All settings are saved to the ini file. The short labels have previously been referred to as ‘point nos’ this is historical in that originally that had to be an integer. This has changed such that they are latterly 8 character strings.

Graphics / Point Long Labels: Toggles the visibility of the template point long labels on the graphical display. The size and colour is user definable. All settings are saved to the ini file. They are referred to ‘long’ to distinguish them from the previous menus ‘short’ label.

Graphics / Point Template Nos: Toggles the visibility for point labeling on the graphical display, showing the points number in the template. The size and colour is user definable. All settings are saved to the ini file. These are the actual point position in the template and are not connected to any user defined label.

Graphics / Point Limits / Visible: Toggles the visibility of the Limit boxes. If this turns the visibility to ‘off’ it will also if necessary set the Use to ‘off’, i.e. the limit boxes can only be in ‘use’ if visible. Toggling the visibility to ‘on’ does not make them in ‘use’, i.e. limit boxes can be visible but not in ‘use’. The in ‘use’ setting is controlled by the next menu item.

Graphics / Point Limits / Use: Toggles the point limit boxes ‘use’ setting. When in use they limit the joggling or dragging of hard points to within the limited region. Limit boxes are also used for tolerance analysis.

Graphics / Point Values: Toggles the visibility of the x,y and z coordinates for the suspension hard points. When ‘on’ the static coordinates are drawn adjacent to each hard point.

Graphics / Template Part Nos: Toggles the visibility of the template part numbers. When ‘on’ the template part numbers are drawn at the geometric centre of each part.

Graphics / Part Labels: Toggles the visibility of the template part labels. When ‘on’ the template part labels are drawn adjacent to the geometric centre of each part.

Graphics / Part C of G Visibility / C of G Marker: Toggles the visibility of the part C of G markers. Part C of G’s can only be drawn when in compliant mode. Part C of G markers are drawn as green and black quadrant style images similar to the body C of G marker.

Graphics / Part C of G Visibility / C of G Axes Points: Toggles the visibility of the part C of G axis points. Part C of G’s can only be drawn when in compliant mode. Part C of G axis points can be picked and dragged as well as edited to re-define the C of G axes. C of G axes are used to orientate local mass properties.

Graphics / Part C of G Visibility / C of G Local Axes: Toggles the visibility of the part C of G local axes. These graphic axes show the current local axes as defined by the local axis points. Part mass properties are defined relative to these local axes.

Graphics / Enhanced Visibility: Controls the visibility of the ‘enhanced’ graphics items. Options are given to switch individual graphic types on and off, Toggle all enhanced graphic types, set them all to ‘on’ or set them all to ‘off’. For the purpose of this menu the ‘Enhanced’ graphics items are, Spring, Damper, Wheel, Bushes, Grid and Body. The other items in this visibility list are not affected by the global ‘enhanced’ status changes, only they’re own individual settings. These are; Triad, Origin Marker, C of G marker, Moving Ground/wheels and Roll axis.

Graphics / Display Ends: Sets the visibility switch for each suspension end. This enables the display to show both, front only or rear only, in a model that contains two axles. Menu has no relevance to a single axle model.

Graphics / Display Both Sides: For visualization enables the viewing of both suspension sides on an axle when the template is defined as a single corner. For full axle templates this switch will have no effect on the graphics display but will change the graph displays. Menu acts as a toggle, so un-check menu to disable viewing.

Graphics / Colours: Provides control over individual plot element colours. Modified colours settings are stored to the users ini file. The elements that can be defined via this menu include; Static Links, Incremental Links, Static Points, Incremental Points, Picked Points, Static Roll Centre Position, Incremental Roll Centre Position, 2D Axis Lines, 3D Drag Lines, Triad, Static 2D Construction Lines, Incremental 2D Construction Lines, Limit Lines (on), Limit lines (off), Point Values and Point Nos.

Graphics / Colours / Set to Defaults: Single menu selection to set all relevant graphics element colours back to the default settings. For relevant elements see previous menu item.

Graphics / Enhanced Colours: Provides control over individual Enhanced plot element colours. Modified colour settings are stored to the users ini file. The elements that can be defined via this menu include; Static Spring, Incremental Spring, Static Damper, Incremental Damper, Static Wheel, Incremental Wheel, Wheel Fill, Static Bushes, Incremental Bushes, Grid, Static Body, Incremental Body and Body Fill.

Graphics / Enhanced Colours / Set to Defaults: Single menu selection to set all relevant enhanced graphics element colours back to the default settings. For relevant elements see previous menu item.

Graphics / Enhanced Sizes / Edit: Displays the Enhanced graphics element sizes for viewing and editing. Changes are stored to the users ini file. Properties that can be edited include; Spring Diameter, No of Spring Coils, Lower Damper Tube Diameter, Upper Damper Tube diameter, Damper No. of Facets, Pivot Diameter, Pivot No. of Facets, Tyre No. of Facets, Tyre Diameter Shoulder ratio, Tyre Width Shoulder Ratio, 3D Tracking Line Length, Joggle Symbol Size, C of G Symbol Size and Ground Plane Grid Size.

Graphics / Enhanced Sizes / Set to Defaults: Single menu selection to set all relevant enhanced graphics element sizes back to the default settings. For relevant elements see previous menu item.

Graphics / Label Sizes / Edit: Displays the current Label sizes for viewing and editing. Changes are stored to the user ini file. Sizes that can be changed are the hard point values size and the hard point number size.

Graphics / Label Sizes / Set to Defaults: Single menu selection to set all relevant label sizes back to the default settings. For relevant elements see previous menu item.

Graphics / Compliance Colours: Provides control over individual compliance plot element colours. Modified colour settings are stored to the users ini file. The compliance elements that can be defined via this menu include; Ball Joint (Rigid), Bush (Compliant), Tyre Spring, External Force and Calculated Force.

Graphics / Compliance Colours / Set to Defaults: Single menu selection to set all relevant compliance graphics element colours back to the default settings. For relevant elements see previous menu item.

Graphics / Compliance Sizes / Edit: Displays the compliance graphics element sizes for viewing and editing. Changes are stored to the users ini file. Properties that can be edited include; Ball Joint Diameter, Ball Joint Circumferential Complexity, Ball Joint Height Complexity, Bush Radius, Bush Length, Bush Circumferential Complexity, Bush Height Complexity, Bush Axis Length, Tyre Spring Diameter, External Force Head, External Force Fixed Length and External/Internal Force Scaled Length.

Graphics / Compliance Sizes / Set to Defaults: Single menu selection to set all relevant compliance graphics element sizes back to the default settings. For relevant elements see previous menu item.

Graphics / Compliance Visibility: Controls the visibility of the ‘compliant’ graphics items. Options are given to switch individual graphic types on and off. For the purpose of this menu the ‘Compliant’ graphics items are, Ball Joints, Bushes, Tyre Spring, Bush Axis points, Bush Local Axis, External Forces, External Force Axis, Calculated Forces and Calculated Force Values.

Graphics / Compliance Visibility / External Force Type: Three types of compliant external force display are available. A fixed length arrow and a fixed size head that does not change with its magnitude or a scaled force vector whose magnitude is multiplied by a graphical length scalar but still with a fixed size head or finally both a scaled length and a scaled head size.

Graphics / Compliance Visibility / Calculated Force Type: Three types of compliant calculated force display are available. A fixed length arrow and a fixed size head that does not change with its magnitude or a scaled force vector whose magnitude is multiplied by a graphical length scalar but still with a fixed size head or finally both a scaled length and a scaled head size.

Graphics / Copy to Clipboard: Copies the current graphical display to the Windows clipboard such that it can be pasted into other applications. Cannot be used with the OpenGL graphics frame.

Graphics / Save to File: Saves the graphics display to a file. Three file formats are supported, bmp, jpg and png.

Graphics / Print / Current View: Prints the current graphics display to a selected printer. The user is prompted, via the standard Windows printer, to identify from the available printers the required settings. This option is currently not available for the OpenGL graphics frame. Only the current view is printed.

Graphics / Print / 4x View: Prints the current graphics display to a selected printer. The user is prompted, via the standard Windows printer, to identify from the available printers the required settings. This option is currently not available for the OpenGL graphics frame. This option prints 4 images on the same page, one for each of the standard views, three orthogonal and the ISO view.

Graphics / Print (to default printer) / Current View: Prints the current graphics display to the current default printer. This option is currently not available for the OpenGL graphics frame. Only the current view is printed.

Graphics / Print (to default printer) / 4x View: Prints the current graphics display to the current default printer. This option is currently not available for the OpenGL graphics frame. This option prints 4 images on the same page, one for each of the standard views, three orthogonal and the ISO view.

Graphics / AVI File Writer…: Opens the AVI file write dialogue. This provides a set of simple to use methods for creating AVI files. Users can create an AVI based on the currently defined displacement, animating over the defined range. Or creating an animation sequence from a series of individual screen shots. The AVI file can be for the full graphics screen or a selected portion. No compression is currently used so whilst file sizes are larger, the issue over LCD projectors being unable to show due to unsupported compression is avoided.

Graphics / Add Graphic / Line / Pnt-Pnt Line: Adds a new Line graphical element to the selected ends’ template. Two hard point picks are required, points need not be on the same part.

Graphics / Add Graphic / Line / Pnt-Vector Line: Adds a new Line graphical element to the selected ends’ template. Three hard point picks are required, a line is drawn through the first point who’s direction is set by the vector defined by the second and third picks, points need not be on the same part. The first and second picks can be the same point. The line is drawn to a global clipped length.

Graphics / Add Graphic / Line / Pnt-Xvector Line: Adds a new Line graphical element to the selected ends’ template. One hard point pick is required, a line is drawn through the picked point in the global X axis direction. The line is drawn to a global clipped length.

Graphics / Add Graphic / Line / Pnt-Yvector Line: Adds a new Line graphical element to the selected ends’ template. One hard point pick is required, a line is drawn through the picked point in the global Y axis direction. The line is drawn to a global clipped length.

Graphics / Add Graphic / Line / Pnt-Zvector Line: Adds a new Line graphical element to the selected ends’ template. One hard point pick is required, a line is drawn through the picked point in the global Z axis direction. The line is drawn to a global clipped length.

Graphics / Add Graphic / Line / Pnt-Plane-Norm: Adds a new Line graphical element to the selected ends’ template. A line is drawn through the selected point in a direction normal to the selected plane. The plane is identified by three point picks. The line is drawn to a global clipped length.

Graphics / Add Graphic / Line / Pnt-UserVector: Adds a new Line graphical element to the selected ends’ template. A line is drawn through the selected point in a direction defined by a user vector. The line is drawn to a global clipped length

Graphics / Add Graphic / Line / Pnt-Vector^Vector : Adds a new Line graphical element to the selected ends’ template. A line is drawn through the selected point in a direction defined by the cross product of two user-selected vectors. The line is drawn to a global clipped length.

Graphics / Add Graphic / Line / Vector-Vector Int X-Vector: Adds a new Line graphical element to the selected ends’ template. A line is drawn along the x-direction through the intersection point of two vectors. Each vectors being defined by two points.

Graphics / Add Graphic / Line / Vector-Vector Int Y-Vector: Adds a new Line graphical element to the selected ends’ template. A line is drawn along the y-direction through the intersection point of two vectors. Each vectors being defined by two points.

Graphics / Add Graphic / Line / Vector-Vector Int Z-Vector: Adds a new Line graphical element to the selected ends’ template. A line is drawn along the z-direction through the intersection point of two vectors. Each vectors being defined by two points.

Graphics / Add Graphic / Line / Pnt-Line Perp Vector-Line: Adds a new Line graphical element to the selected ends’ template. An extended line is drawn through the picked point and a point on the picked line. This second point being the position of a normal to the first point.

Graphics / Add Graphic / Line / Pnt-Pnt Vector-Line: Adds a new Line graphical element to the selected ends’ template. An extended line is drawn through the two picked points. This differs from the earlier option of Pnt-Pnt line in that it is extended to a user specified distance beyond the picked points.

Graphics / Add Graphic / Cylinder / Pivot: Adds a new Pivot graphical element to the selected ends’ template. Two hard point picks are required, both points need not be on the same part.

Graphics / Add Graphic / Cylinder / Tube: Adds a new Tube graphical element to the selected ends’ template. Two hard point picks are required, both points need not be on the same part.

Graphics / Add Graphic / Cylinder / Vector-Radius-Length: Adds a new cylinder graphical element to the selected ends’ template. Drawn through the selected point in a direction defined by the second and third point picks. The radius and length of the cylinder are defined directly.

Graphics / Add Graphic / Cylinder / Pnt-Vector-Radius-Length: Adds a new cylinder graphical element to the selected ends’ template. Drawn through the selected point in a direction defined directly by the user defined vector and of defined cylinder radius and length.

Graphics / Add Graphic / Circle / Pnt-Pnt-Pnt: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required through which is drawn a circle, both the circle centre and radius are calculated and displayed as part of the graphical display.

Graphics / Add Graphic / Circle / Cntr-Rad-Norm: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required. The circle is drawn centered at the first point of a defined radius and who’s normal is defined by the second and third picks. The first and second picks can be the same point.

Graphics / Add Graphic / Circle / Cntr-Pnt-Plane: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required. The circle is drawn centered at the first point and is drawn through the second point, (i.e. defines the radius), in a plane that contains the third picked point. All picked points must be different.

Graphics / Add Graphic / Circle / Pnt-Normal: Adds a new Circle graphical element to the selected ends’ template. Three hard point picks are required. The circle is drawn through the first point about the defined normal vector. All picked points must be different. The derived circle centre and radius is drawn as part of the graphical element display.

Graphics / Add Graphic / Sphere / Pnt-Pnt Radius: Adds a new Sphere graphical element to the selected ends’ template. Two unique hard point picks are required. The sphere is centered at the first pick and the radius is set by the second pick.

Graphics / Add Graphic / Sphere / Pnt Radius: Adds a new Sphere graphical element to the selected ends’ template. One hard point pick is required. The sphere is centered at the pick and given the radius specified by the user.

Graphics / Add Graphic / Sphere / Pnt-Pnt Dia: Adds a new Sphere graphical element to the selected ends’ template. Two unique hard point picks are required. The sphere is centered at the mid point of the two picks, the radius being half the distance between them.

Graphics / Add Graphic / Sphere / Pnt-Pnt-Pnt-Pnt: Adds a new Sphere graphical element to the selected ends’ template. Four unique hard point picks are required. The sphere is drawn through the selected four points. Four points will define a unique sphere who’s calculated radius and centre position is identified as part of the drawn graphical element.

Graphics / Add Graphic / Facet / Pnt-Pnt-Pnt Facet: Adds a new Triangular Facet graphical element to the selected ends’ template. Three hard point picks are required, points need not be on the same part.

Graphics / Add Graphic / Facet / Pnt-Pnt-Pnt-Pnt Facet: Adds a new Four noded Facet graphical element to the selected ends’ template. Four unique hard point picks are required, points need not be on the same part. Whilst points need not be in a plane, any facet drawn of non-planar nodes is not fully defined.

Graphics / Add Graphic / Plane / Pnt-Pnt-Pnt Plane: Adds a plane graphical element to the selected ends’ template. Three unique hard point picks are required, points need not be on the same part. All plane elements are drawn clipped to a global value, (which the user can edit).

Graphics / Add Graphic / Plane / Pnt-X-Y Plane: Adds an X-Y plane graphical element to the selected ends’ template drawn through the selected pick. All plane elements are drawn clipped to a global value, (which the user can edit).

Graphics / Add Graphic / Plane / Pnt-X-Z Plane: Adds an X-Z plane graphical element to the selected ends’ template drawn through the selected pick. All plane elements are drawn clipped to a global value, (which the user can edit).

Graphics / Add Graphic / Plane / Pnt-Y-Z Plane: Adds an Y-Z plane graphical element to the selected ends’ template drawn through the selected pick. All plane elements are drawn clipped to a global value, (which the user can edit).

Graphics / Add Graphic / Plane / Pnt-UserVector Plane: Adds an plane graphical element to the selected ends’ template drawn through the selected pick. The orientation of the plane is controlled by two user defined vectors. All plane elements are drawn clipped to a global value, (which the user can edit).

Graphics / Add Graphic / Components / Pnt-Pnt Comps: Adds a point to point distance graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The display shows the distance between the two points in its x, y and z components. 

Graphics / Add Graphic / Components / Pnt-Line Comps: Adds a point to line distance graphical element to the selected ends’ template. Any three hard point picks are required, all points must be on the same suspension corner. The last two picks define the required line. The display shows the perpendicular distance between the point and the line in its x, y and z components.

Graphics / Add Graphic / Components / Line-Line Comps: Adds a minimum distance between two lines graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first two picks define one line whilst the last two picks define the other required line. The display shows the minimum normal distance between the two lines in its x, y and z components.

Graphics / Add Graphic / Components / Pnt-Plane Comps: Adds a points’ distance from a plane as a graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first point is the required point whilst the last three picks define the required plane. The display shows the normal distance between the point and the plane in its x, y and z components.

Graphics / Add Measure / Distance / Pnt-Pnt Dist: Adds a point to point distance graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The display shows the total distance between the two points.

Graphics / Add Measure / Distance / Pnt-Line Dist: Adds a point to line distance graphical element to the selected ends’ template. Any three hard point picks are required, all points must be on the same suspension corner. The last two picks define the required line. The display shows the total perpendicular distance between the point and the line.

Graphics / Add Measure / Distance / Line-Line Dist: Adds a minimum distance between two lines graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first two picks define one line whilst the last two picks define the other required line. The display shows the minimum normal distance between the two lines as a total distance.

Graphics / Add Measure / Distance / Pnt-Plane Dist: Adds a points’ distance from a plane as a graphical element to the selected ends’ template. Any four hard point picks are required, all points must be on the same suspension corner. The first point is the required point whilst the last three picks define the required plane. The display shows the normal distance between the point and the plane as a total distance.

Graphics / Add Measure / Angle / Pnt-Pnt-Pnt Angle: Adds an angle between three points graphical element to the selected ends’ template. Any three hard point picks are required, all points must be on the same suspension corner. The middle picks is the point for which the angle is given. The display shows the angle created by the three point picks in degrees.

Graphics / Add Measure / Angle / Pnt-Pnt Z-Axis Angle: Adds an angle between two points and the Z-axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees.

Graphics / Add Measure / Angle / Pnt-Pnt Z-Axis X-X Angle: Adds an angle between two points and the Z-axis graphical element to the selected ends’ template, only the angle component about the X-X axis is given. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees.

Graphics / Add Measure / Angle / Pnt-Pnt Z-Axis Y-Y Angle: Adds an angle between two points and the Z-axis graphical element to the selected ends’ template, only the angle component about the Y-Y axis is given. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees. 

Graphics / Add Measure / Angle / Pnt-Pnt X-Axis Angle: Adds an angle between two points and the X-axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The first picks is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees. 

Graphics / Add Measure / Angle / Pnt-Pnt X-Axis Z-Z Angle: Adds an angle between two points and the X-axis graphical element to the selected ends’ template, only the angle component about the Z-Z axis is given. Any two hard point picks are required, both points must be on the same suspension corner. The first picks is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees.

Graphics / Add Measure / Angle / Pnt-Pnt X-Axis Y-Y Angle: Adds an angle between two points and the X-axis graphical element to the selected ends’ template, only the angle component about the Y-Y axis is given. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees.

Graphics / Add Measure / Angle / Pnt-Pnt Y-Axis Angle: Adds an angle between two points and the Y-axis graphical element to the selected ends’ template. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees. 

Graphics / Add Measure / Angle / Pnt-Pnt Y-Axis Z-Z Angle: Adds an angle between two points and the Y-axis graphical element to the selected ends’ template, only the angle component about the Z-Z axis is given. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees.

Graphics / Add Measure / Angle / Pnt-Pnt Y-Axis X-X Angle: Adds an angle between two points and the Y-axis graphical element to the selected ends’ template, only the angle component about the X-X axis is given. Any two hard point picks are required, both points must be on the same suspension corner. The first pick is the start of the vector for which the angle is given. The display shows the angle created by the two point picks and the relevant axis in degrees.

Graphics / Pick Visibility / Limit Box Corners: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the ‘Limit Box’ corners.

Graphics / Pick Visibility / Bush Definition Points: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the Bush definition points.

Graphics / Pick Visibility / C of G Definition Points: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the C of G definition points.

Graphics / Pick Visibility / Local coordinate Axis Definition Points: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the Local coordinate axis systems definition points.

Graphics / Pick Visibility / External Force Definition Points: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the ‘External Force’ definition points.

Graphics / Pick Visibility / Pnt-Pnt Line: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the Pnt-Pnt Line graphical type.

Graphics / Pick Visibility / Pivot: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the Pivot graphical type.

Graphics / Pick Visibility / Tube: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the Tube graphical type.

Graphics / Pick Visibility / Pnt-Pnt-Pnt Facet: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls the pickability of the ‘Pnt-Pnt-Pnt’ Facet graphical type.

Graphics / Pick Visibility / Skip All Graphics: To aid in picking data points in more complex models this menu option together, with other similar ones, enable certain graphical entities to be un-selectable. This menu controls all the graphical types.

+$#>Pull Down Menu Items - Graphs

Graphs / New-Open: Opens a new graph window. Each new graph will by default take the use y-variable from the available list. To change the y-variable once opened use the mouse right button menu options.

Graphs / Visibility: Controls the visibility of the graph items. Options are given to switch individual graph items on and off. For the purpose of this menu the ‘graph’ items are; Grid Lines, Deviation Values, Point Symbols, Data Values, Derivative Values, Scope Line, User Line, Fit Line, Plot Line and Extended Axis Labels.

Graphs / Colours: Provides control over individual graph element colours. Modified colour settings are stored to the users ini file. The graph elements that can be defined via this menu include; Grid Lines, Background, Axis Lines and Text, Border Region, Data Line 2D/3D Front, Data Line 3D Rear, Scope Line 2D/3D Front, Scope Line 3D Rear and User Line.

Graphs / Line Marker: Provides control over individual graph line markers. Modified marker settings are saved to the users ini file. The graph lines that marker types can be defined for are; Data Line 2D/3D Front, Data Line 3D Rear, Scope Line 2D/3D Front, Scope Line 3D Rear and User Line. The nine marker types available are Filled Diamond, Triangle, Inverted Triangle, Plus, Cross, Square, Diamond, Circle and Star.

Graphs / Line Marker / Set to Defaults: Single menu selection to set all relevant graph line marker symbols back to the default settings. For relevant elements see previous menu item.

Graphs / Switch x-y Axis: Changes the visual appearance of the graphs. Swaps the x and y axes around from the normal, such that the ‘y-variable’ is plotted along the horizontal axis rather than the default vertical position.

Graphs / Increment Based X-Axis: Changes the drawing of the X-Axis such that instead of always having the 10 increments, the No of increments varies with the graph range, increment size being defined as a value rather than a fraction of the axis length.

Graphs / Increment Based Y-Axis: Changes the drawing of the Y-Axis such that instead of always having the 6 increments, the No of increments varies with the graph range, increment size being defined as a value rather than a fraction of the axis length.

Graphs / X-Axis Increment Values: Visibility switch for the x-axis labels showing graph increment values.

Graphs / Y-Axis Increment Values: Visibility switch for the y-axis labels showing graph increment values.

Graphs / X-Axis Limit Values: Visibility switch for the x-axis labels showing graph limit values.

Graphs / Y-Axis Limit Values: Visibility switch for the y-axis labels showing graph limit values.

Graphs / Autoscale (All): Autoscales all open graphs for both x and y-axes. Includes all visible lines. To autoscale individual graphs use the mouse right button menu item.

Graphs / Autoscale to Y Increment (All): Autoscales all open graphs y-axes. Includes all visible lines. The autoscaling is based on rounding to the nearest whole number of a specific increment. Each graph variable has its own editable increment setting. This autoscale option can also be applied to individual graphs through the right mouse menu of the specific graph.

Graphs / Scope / On: Controls the visibility of the scope line display. It is also controllable via the visibility settings above.

Graphs / Scope / Store / Exclusive: Takes a copy of the current suspension graph results, (includes all variables not just those that are currently displayed). These scope lines are then ‘fixed’ for comparative on-graph display, (check relevant visibility switch set to ‘on’). The ‘Exclusive’ option implies that the results are copied into Scope position 1, and the four other scope positions (2 to 5) are emptied.

Graphs / Scope / Store / Shuffle: Takes a copy of the current suspension graph results and saves it to scope position 1. All other existing scope data is shuffled down one slot such that one is copied into two etc and any information in position 5 is lost.

Graphs / Scope / Store / Position n: Takes a copy of the current suspension graph results and saves it to scope position n. This will replace any data already stored in this scopes position.

Graphs / Scope / Clear / All: Clears the current scope data from all scope positions 1 to 5. Their isno need to clear the scope before capturing a new set, as Scope Line Store will overwrite any current scope values.

Graphs / Scope / Clear / Position n: Clears the current scope data from the selected position.

Graphs / Scope / List Deviation From / Position n: Identifies which scope position should be used to determine the deviation value between the data and scope lines.

Graphs / Scope / Scope Position Symbol: Sets the visibility of either the scope line symbol or when selected displays a number (1 to 5) rather than the symbol.

Graphs / User Lines / Copy Front-2D Data to User: Convenience function copies the existing 2D or 3D Front result lines to the Users Lines, (all variables are copied over not just the visible ones).

Graphs / User Lines / Copy Rear Data to User: Convenience function copies the existing 3D Rear result lines to the Users Lines, (all variables are copied over not just the visible ones).

Graphs / User Lines / Copy Front-2D Scope to User from / Position n: Convenience function copies the existing 2D or 3D Front scope lines to the Users Lines, (all variables are copied over not just the visible ones). You will need to identify which scope position to use from 1 to 5.

Graphs / User Lines / Copy Rear Scope to User from / Position n: Convenience function copies the existing 3D Rear scope lines to the Users Lines, (all variables are copied over not just the visible ones). You will need to identify which scope position to use from 1 to 5.

Graphs / User Lines / Clear Current User Store: Clears all user defined line data, (all variables are removed not just those currently visible on open graphs)

Graphs / User Lines / Manage User Lines / Create New DataSet…: Multiple user line sets can be managed through the use of User Line data sets. This menu item creates a new data set. Browse for the required folder location and define file name, default extension .dbs. On creation no user line sets are added to the new dataset.

Graphs / User Lines / Manage User Lines / Include DataSet…: Adds an existing user line dataset to the search list. The search list is stored to the users ini file. The search list provides direct access to any stored user line sets that have been added to these DataSets.

Graphs / User Lines / Manage User Lines / Remove DataSet: removes the selected user line data set from the search list.

Graphs / User Lines / Manage User Lines / Load From: Provides a list of found user line sets that can be loaded from the data sets. The loaded user line data will replace any current values.

Graphs / User Lines / Manage User Lines / Add Current to: Option to save the current user line data to one of the current datasets on the search list.

Graphs / User Lines / Manage User Lines / Delete From: Option to remove a stored user line set from one of the current datasets on the search list. User line sets a re identified by the dataset label and line set label.

Graphs / Marker Text Sizes / Edit Sizes: Displays the graph marker and text sizes for viewing and editing. Changes are stored to the users ini file. Properties that can be edited include; Data Line Marker Size, Scope Line Marker Size, User Line Marker Size, Graph Data Values Text Size, Compliance Title Text Size, Compliance Label Text Size and Compliance Values Text Size.

Graphs / Marker Text Sizes / Set to Defaults: Single menu selection to set all relevant graph marker and text sizes back to the default settings. For relevant elements see previous menu item.

Graphs / Decimal Points Display / Edit Settings: Displays the graph decimal points display for viewing and editing. Changes are stored to the users ini file. Properties that can be edited include; X-Data Listing, Y-Data Listing, Derivative Data Listing, Scope Deviation, User Deviation, X-Axis Label, Y-Axis Label and Compliance Graph Values.

Graphs / Decimal Points Display / Set to Defaults: Single menu selection to set all relevant graph decimal points displays back to the default settings. For relevant elements see previous menu item.

Graphs / Print All / 1 to Page / 3 to Page / 4 to Page / 6 to Page / 8 to Page…: Single menu selection to print all open graphs. The user is prompted to select the required printer from those currently available. Specific menu options are given for 1,3,4,6 or 8 to a page. As many pages as required are printed to accommodate all open graphs at the selected number per page.

Graphs / Print All (to default Printer) / 1 to Page / 3 to Page / 4 to Page / 6 to Page / 8 to Page: Single menu selection to print to the current default printer all open graphs. Specific menu options are given for 1,3,4,6 or 8 to a page. As many pages as required are printed to accommodate all open graphs at the selected number per page.

Graphs / Printer Properties…: Option to set default printer and its properties.

+$#>Pull Down Menu Items - Solve

Solve / Motion / Toggle: Switches the solution type between moving ground plane or moving body. It is only applicable to the bump and combined articulation modules.

Solve / Motion / Ground Plane: Switches the solution type specifically to moving ground plane. It is only applicable to the bump and combined articulation modules.

Solve / Motion / Ground Plane Options / move TCP Z: Switches the ground plane point to be the tyre contact point. This is the default ground plane solution type. Thus defined ‘z’ displacement values refer to displacement (or position) of the tyre contact point. It is only applicable to the bump and combined articulation modules and then only when the motion is set to ‘moving ground plane’.

Solve / Motion / Ground Plane Options / move Wheel Centre Z: Switches the ground plane point to be the wheel centre point. Thus defined ‘z’ displacement values refer to the displacement (or position) of the wheel centre. It is only applicable to the bump and combined articulation modules and then only when the motion is set to ‘moving ground plane’.

Solve / Motion / Ground Plane Options / move Lower Ball Joint Z: Switches the ground plane point to be the lower ball joint point (assuming identified in the template). Thus defined ‘z’ displacement values refer to the displacement (or position) of the lower ball joint. It is only applicable to the bump and combined articulation modules and then only when the motion is set to ‘moving ground plane’.

Solve / Motion / Ground Plane Options / move Upper Ball Joint Z: Switches the ground plane point to be the upper ball joint point (assuming identified in the template). Thus defined ‘z’ displacement values refer to the displacement (or position) of the upper ball joint. It is only applicable to the bump and combined articulation modules and then only when the motion is set to ‘moving ground plane’.

Solve / Motion / Ground Plane Options / Opposed Bump Z: This option when switched ‘on’ displaces the left and right hand wheels in opposite directions. The default ‘off’, has both wheels moving in the same direction. It is only applicable to the bump and combined articulation modules and then only when the motion is set to ‘moving ground plane’.

Solve / Motion / Ground Plane Options / Z Displacement as Position: This option when switched ‘on’ takes the defined ‘z’ bump values as being the absolute value of the ground plane point. When switched ‘off’ (default) the ‘z’ values are taken as the displacement value for the ground plane point. It is only applicable to the bump and combined articulation modules and then only when the motion is set to ‘moving ground plane’.

Solve / Motion / Steering Options / Y Displacement as Position: This option when switched ‘on’ takes the defined ‘y’ steering values as being the absolute value of the steering point. When switched ‘off’ (default) the ‘y’ values are taken as the displacement value for the steering point. It is only applicable to the bump and combined articulation modules.

Solve / Motion / Body: Switches the solution type specifically to moving body. It is only applicable to the bump and combined articulation modules.

Solve / Motion / Solve By Number of Steps: This option when switched ‘on’ solves at the defined number of steps between the specified travel limits rather than using the user defined increment.

Solve / 2D Fix Option: For the 2D module a number of alternative solution techniques can be employed. This sets which hard point, if any, is ‘freed’ off to match the target characteristics.

Solve / 3D Compliance: Turns on the compliant solver. Compliant solutions add elastic bushes and external force effects on to the incremental kinematic solution.

Solve / External Forces: For compliance analysis, external forces can be optionally included. Toggles through on/off with this menu option or use the equivalent toolbar icon.

Solve / Spring Kinematic Displacement Force: For compliance analysis, the suspension spring pre-load force due to the kinematic displacement can be optionally included. Toggles through on/off with this menu option.

Solve / Spring Rate: For compliance analysis, the suspension spring rate can be optionally included in the stiffness matrix. Toggles through on/off with this menu option. Turning the spring rate off also implies that the spring kinematic displacement force will also not be included.

Solve / Roll Bar Kinematic Displacement Force: For compliance analysis, the suspension roll bar force (if modeled) due to the kinematic roll displacement can be optionally included. Toggles through on/off with this menu option.

Solve / Roll Bar Rate: For compliance analysis, the suspension roll bar rate can be optionally included in the stiffness matrix. Toggles through on/off with this menu option. Turning the roll bar rate off also implies that the roll bar kinematic displacement force will also not be included.

Solve / Bump Stop Kinematic Displacement Force: For compliance analysis, the suspension bump stop force due to the kinematic displacement can be optionally included. Toggles through on/off with this menu option.

Solve / Bump Stop Rate: For compliance analysis, the suspension bump stop rate can be optionally included in the stiffness matrix. Toggles through on/off with this menu option. Turning the bump stop rate off also implies that the bump stop kinematic displacement force will also not be included.

Solve / Bush Kinematic Rotation loads: For compliance analysis, the implied pre-loads of the bush due to the incremental kinematic rotation will be included when this option is enabled at each calculated step. By definition at static ride when there is no displacement the pre-loads will be zero.

Solve / Tyre Vertical Rate: For compliance analysis, the tyre vertical rate can be optionally included in the stiffness matrix. Toggles through on/off with this menu option. This would normally be set to ‘on’ but in specific load cases users may wish to turn this of to inspect a particular force path.

Solve / Control Elements: Models that have length or position control elements included their impact on the kinematic solution can be toggles ‘on’ and ‘off’ with this menu. Note that turning them off also has the effect of not drawing them even if the specific visibility option is set to ‘on’.

Solve / Control Elements / One Step Delay: With some control elements for solver stability it is necessary to have a one step delay in applying the change in position/length. Toggling this menu item switches between direct application and a one step delay.

Solve / Control Elements / Iteration Limits: Controls the limits for applying control elements. This restricts infinite loops where the solver can’t converge.

Solve / Drive Shaft Loads: In compliance mode this option toggles the inclusion of drive shaft loads. Drive shaft points need to be included in the template and applied torque’s defined before this has any impact on the compliance calculation.

Solve / Non Linear Rack Bush: In compliance mode this option enables the non-linear rack bush. The solver performs a two step compliant solution to identify the force in the rack bush and then modify the applied forces to achieve the correct non-linear displacement for the force. Requires a non-linear rack bush to be defined.

Solve / Un-Braked Hub: In compliance mode this option toggles whether external longitudinal forces are reacted on the upright or by the drive shaft. The ‘braked’ option is the default and the longitudinal wheel/hub forces are reacted as though the brakes were applied and the loads are reacted by the upright. If the ‘braked’ option is not set then the loads are reacted by the drive shaft and thus fed back into the model as a reactive drive torque. This non-braked option requires that the drive shafts are included in the model.

Solve / Convert 2D to 3D: Convenience routine to convert existing 2D model data to selected 3D suspension.

Solve / Display Optimizer: Toggles the visibility of the display that not only lists the cumulative sum of all weighted deviations but also controls the sensitivity and optimization functions. These optimization settings include individual curve weightings, parameters required and range of interest. 

Solve / Wheelbase Diff Sol: Controls how a difference in the wheelbase is handled when adding a second axle to an existing model. If a difference is found between the wheelbase parameter and the distance between the two axle wheel centers, this option will determine whether the wheelbase parameter is adjusted, or the rear suspension is moved to match the wheelbase parameter.

Solve / Grnd Plane Diff Sol: Controls how a difference in the ground plane position is handled when adding a second axle to an existing model. If a difference is found between the two ground plane values, this option will determine whether the difference is accommodated by translation, roll or bump/rebound corrections.

Solve / Solver Tolerances: Displays the current solution tolerances for viewing and editing. Solution tolerances listed include The kinematic solution tolerance, the kinematic warning level tolerance, Bump small perturbation size and Steer small perturbation size.

Solve / Solver Method / Gaussian Elimination / Cholesky Decomposition: Defines the solution method for the compliant analysis. The original solver version used the slower but more robust Gaussian Elimination method. This method is available for backward compatibility although no change in the results should be seen using the later Cholesky Decomposition (other than a 4x speed increase). In the event of a solution fail with the Cholesky method the solver automatically reverts to Gaussian elimination.

Solve / Report Errors (brief): Switches the ‘brief’ error-reporting on/off. Gives a summary message if any errors found during the solution. For greater reported information see option below.

Solve / Report Errors (full): Switches the ‘full’ error-reporting on/off. The display indicates which calculation steps cause a problem and where the problem is in the solution process.

Solve / Run Virtual Compliance Test: This option provides a data link between the two modules of Lotus Suspension Analysis. The full vehicle handling module requires a number of splines that define the motion of the un-sprung corner masses under a variety of loading and displacement conditions. This data would conventionally come from physical testing of a vehicle on a SKCMS rig. This option allows you to take a Shark full vehicle compliant model and run it through a series of ‘virtual’ tests to produce these splines. This option is only available for models with both front and rear suspensions defined. To produce valid results any anti roll bars and the compliant steering rack option should be included in your model. Whilst this option will still run if these are not added the opposed and parallel tests will not correctly identify the cross car force linking if not added.

Solve / Virtual Compliance Test Settings: Opens a spread sheet that lists the individual test used in the Virtual SKCMS process and the individual settings for these tests. These settings are saved to the users INI file and allow for both an understanding of the virtual tests and the means to manipulate as required.

+$#>Pull Down Menu Items - Results

Results / Formatted SDF…: Opens the Suspension Derivative File (SDF). This scrollable textual display lists the an echo of the suspension hard points and incremental listings of the relevant suspension characteristics for all articulation types. The user can edit how many tables and what columns appear in each table. A number of standard settings can be defined by the user each saved to a ‘position’.

Results / SDF Spline Fits…: Opens the Suspension Derivative Spline Fits display. This scrollable textual display lists the an echo of the suspension hard points and listings of the spline fit equations for the selected suspension characteristics for all selected articulation types. The spline fit types include Linear, quadratic and cubic. 

Results / SDF Spline Data…: Opens the Suspension Derivative Spline Data display. This scrollable textual display lists the an echo of the suspension hard points and listings of each splines data points. The user can control which splines are listed as well as inclusion of header information and data echo.

Results / Std SDF Scale and Shift Settings…: Opens a spread sheet that allows user to apply unique scale and shift values to each standard SDF, with different values being applied to each corner. In this way a user can customize the results to suit their own particular sign convention. This Scale and shift values are in addition to any changes made through the ‘Units’ settings.

Results / Edit User Defined Results…: Opens the dialogue box for user creation of their own results. Results created in this way then become available for all graphing and listing actions. User defined SDF’s are built up via a string recognition editor that can include existing standard SDF’s, point positions, point forces and math’s functions. The utility also has the option to save/read these user SDF’s to and from an external file, such that they can be shared between users.

Results / Formatted Bush Values…: Opens the scrollable text listing a summary of the defined bush properties. This includes the Zp vector the Xp vector and bush rates used.

Results / Bush Deflections…: Opens the scrollable text listing of bush deflections for compliant models under the current force set.

Results / Joint-Bush Rotations…: Opens the scrollable text listing of bush rotations for compliant models under the current zero set load conditions.

Results / Bush Forces…: Opens the scrollable text listing of bush forces for compliant models under the current zero set load conditions.

Results / Formatted Point Forces…: Opens the scrollable text listing of point forces for compliant models. The formatting control allows the point force results to be tabulated for any defined load condition.

Results / UnSprung Corner Weights…: Performs a specific compliant analysis task by applying a ‘Gravity’ force to each component C of G. This identifies the change in tyre vertical force and hence the unsprung corner weight. As this option requires the compliant solver you need to be in compliant mode to list these results. The corner weights are displayed in a specific dialogue box through which you can adjust part masses.

{bmc bm176.bmp}
Corner Weights Calculation.

Results / List All Point Coords for User Position…: Option to list suspension hard points at a user defined bump, roll and steer position. Define the required bump value, (+ve is in bump) roll angle and steer value.

Results / List a Point Coords at All Positions…: Option to list the co-ordinates of a single selected suspension hard point at all current solution positions. User selects the required corner and point. The resultant textual display has full support for printing, saving and exporting.

Results / List All Point Coords at a Positions…: This is the inverse of the previous option. It lists the co-ordinates of all points for a single selected position. The position is one from the current solver settings rather than a separately user defined position. User selects the required corner and position. The resultant textual display has full support for printing, saving and exporting.

Results / Compliance Text Values: Opens the text listing of the Compliance coefficients. This displays the same values as shown graphically (see the next menu item).

Results / Compliance Bar Values: Toggles the visibility of the Compliance bar charts coefficients display.

Results / Ball Joint Rotations: Toggles the visibility of the Ball Joint rotations display. This option is only available in compliant mode. The results show the rotations of a selected joint over the prescribed travel. These rotations can be relative to local or global axes or to a pair of user defined points that identify the housing and ball axes.

Results / Modal Analysis Display..: Opens the Modal Analysis bar chart display. The display shows the frequency of each mode by the height of its bar. This option is only available in compliant mode. This display can be used to change the mode displayed in the 3d view, (the current mode is shown filled in ‘cyan’), by selecting the required modes bar with the left mouse button. This graph can be left open and is updated ‘live’ as the model is changed.

Results / Forced-Damped Speed Sweep Display..: Opens the Forced-Damped Results graph.  This shows the displacement and rotation of each parts C of G at the specified frequency. The currently displayed frequency point in the 3d view is show on the graph by the vertical line. The currently displayed 3d view frequency can be changed by selecting the required point on the graph using the left mouse button. Whilst this graph display can be left open whilst you continue to edit the model it does not update in a ‘live’ manner due to the associated computational overheads. To update this display select from its right mouse menu list Refresh Plot.

+$#>Pull Down Menu Items - SetUp

SetUp / Start Options / Toolbar Icons: Provides an option for two styles of icons. Select from either Standard or Mouse Sensitive. Standard icons have permanently visible boundaries to the icon, whilst mouse sensitive icons ‘raise’ as the mouse passes over them. This change is stored to the ini file and will only be implemented on next program start-up.

SetUp / Start Options / Toolbar Position: Sets the default starting position for the toolbars. All visible toolbars will be placed in this position when the application starts up. Once started the user can choose to change the toolbar positions individually as required. The four available positions are Top, Bottom, Left or Right. This change is stored to the ini file and will only be implemented on the next program start-up.

SetUp / Start Options / Maximised: If checked defines that the application will start up with the main window maximised, (i.e. expanded to fill the current screen size). Note that if the application is maximised during use, then this will also set the ‘maximised’ setting. This change is stored to the ini file and will be implemented on next program start-up.

SetUp / Exception Handler On: Provides a software trapping routine to handle application exception failures. Whilst this won’t enable the user to recover the current session it will prevent the exception causing a complete system failure. Not normally required this release.

SetUp / Visual Graphics Cursor: When enabled changes the appearance of the cursor on the main graphical display to indicate the difference between the various modes of dynamic view and on-screen editing. This setting is saved to the users ini file.

SetUp / Data Sheet Images: Toggles the visibility of graphical images displayed on the side of the data sheets. This is purely a visual setting.

SetUp / Include User Graphics In Data Files: With the ability for users to quickly add their own graphical elements to the current template the option is given for users to include them with the data file. This provides a complete way of retaining data that is associated with the model.

SetUp / Include User Templates In Data Files: With the ability for users to quickly modify the template by point addition etc. the option is given for users to include the template with the data file. This provides a complete way of retaining data that is associated with the model.

SetUp / Include Optimizer Settings in Data Files: When checked provides data retention/continuity by including the optimizer settings as a sub-section of the model data file. Other wise these data settings could be lost through subsequent use.

SetUp / Include Force Sets in Data Files: When checked provides data retention/continuity by including the defined force set settings as a sub-section of the model data file. Other wise these data settings could be lost through subsequent use.

SetUp / Toolbar Visibility: Sets the visibility option for the individual toolbars. This setting is saved to the ini file and will thus be applied to future runs.

SetUp / Set Toolbars to: Sets the settings for the toolbars either to the original ‘classic’ layout or one of the revised options. Toolbar icon settings are saved to the ini file and will thus be applied to future runs.
 
SetUp / Customize Toolbars…: Opens the toolbar editing tool that allows user to individually customize the toolbars to suit their own user preferences. Toolbar icon settings are saved to the ini file and will thus be applied to future runs.

SetUp / Gen Defaults: Opens the general defaults data set for viewing and editing. They primarily deal with settings for the graphics display. They include upper and lower limits to the scaling, the tolerance for point picking, the tolerance for point coincidence, the joggle coarse step size and the animation refresh time step.

SetUp / Printer Properties: Displays the standard Windows printer dialogue box, to enable default printer and its properties to be set.

SetUp / Undo Buffer Length: Sets the length of the undo buffer. The greater the number the more undo steps that will be stored. Setting this value to zero will disable the undo function.

SetUp / Re-run Search for Installed Components..: Runs the process that scans the users system for installed applications such as Word, Excel and Matlab. This process is run automatically the first time the software is used after installation but this user-invoked option is available to enable subsequent changes to other applications to be re-checked for.

SetUp / Edit Installed Component Executables ..: Define the default executables of external applications that are used by the application. These include ‘Word’, ‘Internet Explorer’, ‘Excel’, ‘Adobe’ and ‘Matlab’.

SetUp / Edit <database> folder location..: Define/edit the location of the database folder. This folder is used as a depository for standard files, templates and default INI file settings.

SetUp / Language / User Defined…: The default language for all menus is English. The option is given for a user to switch to their own defined language via this menu option. It uses a string by string substitution for each item given in the library. This string substitution must first be entered by the user Thus a user need only change as few (or as many) strings as they require. Any user defined language change is stored in a user language library (filename _Custom.dic) and this can be shared between users.

SetUp / Language / Edit User Language…: Opens the dialogue box through which the user defined language is edited. In some user specific cases this will be password protected, (consult your system support if you require password access).

{bmc bm177.bmp}
User Language Editing.

SetUp / Change Units: Opens the utility for setting the Angle, Length, Force and Mass display units. Options are given for each as well as an option to have a user defined unit display.

SetUp / Set Background Colour…: Opens a standard colour selection dialog to pick a new colour for the background colour used in the graphics display. Note that graphs have their ow ncolour settings and are not affected by this change.

SetUp / Graphics Frame Type: Sets the graphics frame device type as either Windows GDI or Open GL. The default device driver is a Windows GDI, (View / Graphics Frame Type / Windows GDI), which whilst it works with all Hardware options does so at the expense of both speed and capability. The GDI driver is unable to support depth buffered display and hence the view styles View / Fill Style / Hidden Line and View / Fill Style / Depth Buffered (Flat shaded ) do not function correctly. The alternative device driver is Open GL, (View / Graphics Frame Type / Open GL), which is both faster and supports depth buffering/hidden line display types and also segmentation (see below).

Not all hardware is able to use the Open GL device type, typical failures are inability to refresh and lack of correct hidden line display. It is often possible to enable OpenGL to work correctly by reducing the amount of hardware acceleration used by the graphics card.

SetUp / Use Segment Display with OpenGL graphics frames the use of segmentation provides a significant improvement in both dynamic viewing and animation refresh speeds. This is because only the segment needs to be refreshed rather than recreate the construction of all the graphics primitives. This is particularly beneficial with animating modes of complex compliant full axle models.

SetUp / Use Software Double Buffer the use of this option allows the OpenGL graphics frames to be used with any level of hardware acceleration being set. Without this option being switched on some hardware setups will not correctly animate or update the dynamic viewing options when using OpenGL.

SetUp / Default Graphical File Type: Sets the default graphical file type used in printing etc. for report file generation as either Bitmap or JPEG.

+$#>Pull Down Menu Items - Window

Window / Tile Horizontal: Automatic window positioning option that lays open windows in to a primarily horizontal layout.

Window / Tile Vertical (Picked Order): Automatic window positioning option that lays open windows in to a primarily vertical layout. The order that they are arranged in is the order that they have been selected, on start-up this would be the inverse of the order that they were created in.

Window / Tile Vertical (Created Order): Automatic window positioning option that lays open windows in to a primarily vertical layout. The order that they are arranged in is based on the creation order with the graphics display first and then graphs 1 to n.

Window / Cascade: Automatic window positioning option. All open windows are re-sized to a common size and cascaded down from the top left hand corner in regular steps.

Window / Save Def. Window Settings: When set this options will save to the users ini file the current size, positions and settings of the graphics and graph windows, such that on a subsequent program start-up all windows will be re-created in the same position/size as previously. They are referred to ‘default’ since users can store different settings to alternative files.

Window / Save Window Settings to…: This option allows the user to save the current window and graph settings to a file. These settings can then be retrieved at a later stage or in future runs.

Window / Load Window Settings from…: This option allows the user to retrieve from a previously saved file the settings for the main window and graphs. These settings included not only position and size but also displayed variables and axis settings.

Window / Edit Window Offsets…: This option allows the user to specify the values used to determine the position of each window within the MDI interface. These may need to be changed by the user if you find yourself repeatedly having to re-position graph windows despite having used the ‘save window settings’ option.

Window / View Custom Control Display: Pick from list to open a previously defined custom control display. Custom controls are added to this list as they are created by the user using the following menu option. When permanently deleted using the WinDelete option, they are removed from this list.

Window / Open New Custom Control Display: Creates a new custom control display dialogue box. Users can add their own buttons, toggles, icons, gauges, sliders, text entries, value entries, bar charts and bars widgets to it. Data variables and commands can be assigned to these widgets to allow users to build their own specific interfaces. Within each window users can switch between use/edit modes to move, add, and edit widgets. Custom dialogue settings are saved to the users ini file for subsequent reuse. Users can save custom dialogue settings to and from external files. This provides a method of passing custom settings between users.

Window / Delete Custom Control Display: Pick from the list of currently defined custom control displays to delete. This will remove it from the settings.

Window / Backdrop: Option to add a graphic image to the background of the main window. Six default options are provided together with an option for a user defined bitmap. The background image can be optionally tiled to repeat the pattern over the entire region. Alternatively if not tiled the image will be stretched to fill the area.

Window / User Backdrop File…: File browser to identify the user specified backdrop bitmap.

Window / Tile Backdrop: Defines whether backdrop image will be stretched or tiled to fill the area.

The Window menu has appended to it an entry for each child window. Child windows include graphic displays all graphs and results displays.

+$#>Pull Down Menu Items - Help

Help / Contents (F1): Opens this help file at the contents page.

Help / Search for Help On…: Opens this help file at the ’index’ page to allow for searching through the help file by key words.

Help / How to Use Help: Opens the standard Windows® Help document, describing how to use on-line help files.

Help / Open Getting Started: Shortcut menu to open the supplied ‘Getting Started’ document from the <install> folder.

Help / About Lotus Suspension Analysis…: Displays the Lotus Suspension Analysis ‘about’ box listing both the major and minor release levels. Support contact details are also given.

+$#>Mouse Right Button Menu Items – Graphics
	
No specific menus are used on the graphics display for the right mouse button, Instead it is used as a quick cycle through the available tracking directions or cycle through the dynamic viewing modes as appropriate for the current dynamic viewing status.

In the view zoom mode the right mouse button will cancel the zoom event.

+$#>Mouse Right Button Menu Items – Graphs

X-Variable (SDF): Used to change the displayed x-variable for the selected graph. Lists all available options, (some may not be relevant to the current module or model). The current variable is shown checked in the list. The list is broken down into five sub menus, ‘Standard’, ‘Positional’, ‘Extended’, ‘d/z’ and ‘§dz’. The sub division is somewhat arbitrary but is due to the large number of SDF’s available.

X-Variable (Front Graphic): Used to change the displayed x-variable for the selected graph to one from the current front suspension graphical elements. Lists all available options, (some may not actually have a plotable result). The current variable is shown checked in the list. This menu is omitted for rear suspension only models.

X-Variable (Rear Graphic): Used to change the displayed x-variable for the selected graph to one from the current rear suspension graphical elements. Lists all available options, (some may not actually have a plotable result). The current variable is shown checked in the list. This menu is omitted for front suspension only models.

X-Variable (User SDF): Used to change the displayed x-variable for the selected graph to one from the current available user defined SDF’s. If no user SDF’s have been previously created this list will be empty.

Y-Variable (SDF): Used to change the displayed y-variable for the selected graph. Lists all available options, (some may not be relevant to the current module or model). The current variable is shown checked in the list. The list is broken down into five sub menus, ‘Standard’, ‘Positional’, ‘Extended’, ‘d/z’ and ‘§dz’. The sub division is somewhat arbitrary but is due to the large number of SDF’s available.

Y-Variable (Front Graphic): Used to change the displayed y-variable for the selected graph to one from the current front suspension graphical elements. Lists all available options, (some may not actually have a plotable result). The current variable is shown checked in the list.

Y-Variable (Rear Graphic): Used to change the displayed y-variable for the selected graph to one from the current rear suspension graphical elements. Lists all available options, (some may not actually have a plotable result). The current variable is shown checked in the list.

Y-Variable (User SDF): Used to change the displayed y-variable for the selected graph to one from the current available user defined SDF’s. If no user SDF’s have been previously created this list will be empty.

User Line Edit / Edit Front (+Y) User Line: Lists the selected graphs’ user line for viewing and editing. The number of points well as the x and y values can edited. On closure the user line data is checked for ascending order on the x-values, if not ascending the data is shuffled unit it is. Not that individual user lines are defined for each corner. This is for the front +Y corner.

User Line Edit / Edit Front (-Y) User Line: Lists the selected graphs’ user line for viewing and editing. The number of points well as the x and y values can edited. On closure the user line data is checked for ascending order on the x-values, if not ascending the data is shuffled unit it is. Not that individual user lines are defined for each corner. This is for the front -Y corner.

User Line Edit / Edit Rear (+Y) User Line: Lists the selected graphs’ user line for viewing and editing. The number of points well as the x and y values can edited. On closure the user line data is checked for ascending order on the x-values, if not ascending the data is shuffled unit it is. Not that individual user lines are defined for each corner. This is for the rear +Y corner.

User Line Edit / Edit Rear (-Y) User Line: Lists the selected graphs’ user line for viewing and editing. The number of points well as the x and y values can edited. On closure the user line data is checked for ascending order on the x-values, if not ascending the data is shuffled unit it is. Not that individual user lines are defined for each corner. This is for the rear -Y corner.

Autoscale: Autoscales the selected graph for both x and y-axes. Includes all visible lines on the graph. To autoscale all graphs use the main menu or equivalent toolbar icon.

Autoscale Y only: Autoscales the selected graph for just its y-axes. Includes all visible lines on the graph. To autoscale all graphs use the main menu or equivalent toolbar icon.

Autoscale to Y Increment: Autoscales the selected graph for just its y-axes. Includes all visible lines on the graph. The autoscale function is based rounding to a specified increment. The increment being definable for each individual graph. To edit the increment refer to the ‘Axis Scales’ right mouse menu option.

Zoom: Pick the area of the selected graph to fit the current window. The zoom function can accommodate either a two press approach to area selection or a single press, hold and drag selection, a simple time delay trap being used to identify which type is being used. The zoomed area will become the plotted region.

Plot as Derivative: By default a graph is plotted for the selected x and y variables exactly as calculated. This graph by graph option allows the user to plot x against dy (i.e. the derivative) of the selected y-variable.

Plot as Integral: By default a graph is plotted for the selected x and y variables exactly as calculated. This graph by graph option allows the user to plot x against §y (i.e. the integral) of the selected y-variable. Note that the constant of integration is adjusted such that the integral is zero for its first point.

Plot as Left and Right: The menu item is only present if both left and right hand sides are being plotted on the display/graphs. This is the default mode in that the left and right hand lines are drawn as separate lines, thus ‘left and right’.

Plot as Left - Right: The menu item is only present if both left and right hand sides are being plotted on the display/graphs. This option plots the numerical sum of left minus right as a single line, thus ‘left - right’.

Plot as Left + Right: The menu item is only present if both left and right hand sides are being plotted on the display/graphs. This option plots the numerical sum of left plus right as a single line, thus ‘left + right’ /2.

Plot as [Left – Right]/2: The menu item is only present if both left and right hand sides are being plotted on the display/graphs. This option plots the average of the numerical sum of left minus right as a single line, thus ‘left - right’ /2.

Plot as [Left + Right]/2: The menu item is only present if both left and right hand sides are being plotted on the display/graphs. This option plots the average of the numerical sum of left plus right as a single line, thus ‘left + right’.

Copy Front Data to User: Convenience function copies the existing Front result line to the User Line. Only the selected graphs’ values are copied over.

Copy Rear Data to User: Convenience function copies the existing Rear result line to the User Line. Only the selected graphs’ values are copied over.

Copy Front Scope to User from / Position n: Convenience function copies the existing Front scope line to the User Line. Only the selected graphs’ values are copied over. You need to identify which scope position you are copying from.

Copy Rear Scope to User from / Position n: Convenience function copies the existing Rear scope line to the User Line. Only the selected graphs’ values are copied over. You need to identify which scope position you are copying from.

Axis Scales: Displays the selected graphs x and y-axis settings. Axes are defined simply by the minimum and maximum values. This display also lists the value used for the autoscale to Y increment option.

Set All X-axis to Displ. Range: Sets the x-axis settings for all the graphs to the limits of the currently defined suspension travel.

Edit All X-axis Scale: Displays the x-axis scale edit box. The displayed values will be the current settings for the selected graph. All graphs will have their x-axis values set to the entered numbers.

List Data Line(s): Lists the selected graphs current results (data) line for viewing. As these are calculated results they are display only. Both front and rear axles are listed, (if applicable).

Copy to Clipboard: Copies the selected graph display to the Windows clipboard such that it can be pasted into other applications.

Save to File…: Saves the selected graph to file. Three format types are currently supported, bmp, jpg and png.

Print…: Prints the selected graph. The user is presented with the standard Windows printer dialogue box to select the required printer/settings.

Print (to default printer): Prints the selected graph to the default printer using the current printer settings.

Printer Properties…: Opens the standard Windows printer dialogue box to set the default printer and its current settings.

Open in MATLAB: Opens the selected graph directly in Matlab as a graph. This thus provides a 'one-click' option to pass graph data from Shark to Matlab. If this option is greyed out then the application has been unable to identify the location of the Matlab product, normally because it is not installed on the machine. If it has been subsequently installed users can re-scan for the Matlab product via the menu option Setup / Re-run search for installed components.

Open in EXCEL: Opens a new Excel worksheet filled with the selected graphs data values. This thus provides a 'one-click' option to pass graph data from Shark to Excel. If this option is greyed out then the application has been unable to identify the location of the Excel executable, normally because it is not installed on the machine. If it has been subsequently installed users can re-scan for the Excel executable via the menu option Setup / Re-run search for installed components.

Export to EXCEL / As New File: Similar to the ‘open’ option above but uses a software link to import the graph into Excel with greater control and functionality. This menu opens in Excel as a new file.

Export to EXCEL / As New worksheet in Current: Similar to the ‘open’ option above but uses a software link to import the graph into Excel with greater control and functionality. This menu opens the graph data in Excel as a new worksheet in the ‘current’ file. The definition of the ‘current’ file is based around the last open session of Excel and is controlled by a Windows environment variable.

Export to EXCEL / As New worksheet in…: Similar to the ‘open’ option above but uses a software link to import the graph into Excel with greater control and functionality. This menu opens the graph data in Excel as a new worksheet in the user specified file. A standard Windows file browser is opened for the user to locate the required file.

+$#>Mouse Right Button Menu Items – Compliance Coefficients

The right mouse menu on the compliance coefficients display has two forms the long form and the short form. The long form is listed if the selection is within a bar region of the chart and the short form is the pick is on the chart but not on a ‘bar’.

Y Variable: Used to change the displayed y-variable for the selected bar. Lists all available options, (some may not be relevant to the current module or model). The current bars variable is shown checked in the list.

Edit Limit Setting: Displays for viewing and editing, the selected bars’ design limit value. This is used to draw a horizontal line on the bar chart as a visual indicator of the analysis results.

Edit Scale Setting: Displays for viewing and editing, the selected bars’ full-scale deflection value. This should be adjusted to encompass the required/anticipated limit.

Edit Weighting Setting: Displays for viewing and editing, the selected bars’ weighting value used to calculate the combined summation of selected variables. This effects the optimization and total sum display.

Remove Selected Variable: .Removes the selected bar from its force sets graph.

Add Extra Variable: For the selected force sets’ graph, an extra variable is added to the display. This variable is changed via the Y-variable menu option.

Set All Limit Values to Current:  For all defined compliance bars the ‘Limit’ value is set to the current value. This is a convenience feature that quickly defines a complete set of limits.

Autoscale All Visible Lines:  All defined compliance bars have the Scale settings set to the current values, with a clip margin. This enables all compliance factors to be visible through a single menu selection.

Set All Visible Line Scales to Unity:  All defined compliance bars have the Scale settings set to unity. This enables all compliance factor scale settings to be returned to unity through a single menu selection.

Edit All Line Limits/Scale/Weights…:  Opens a display window that allows all Limits, Scales and Weightings for the compliance curves to be edited through a single display rather than by picking individually.

Include Spring Force in Set: For the selected force set toggles whether the spring force is included in the compliant calculation.

Make Force Set Default: Makes the selected force set the current one. The current one is indicated by the red highlight, and becomes the force set displayed on the graphics and graphs.

Turn Force Set ‘Off’: turns the status of the selected force set to ‘off’. Its data is not lost but it will not be used in the calculations and its compliant chart will be removed from the display.

Turn All Force Sets ‘On’: Sets all defined force sets to ‘on’. Each force set will then have its own graph displayed.

Open External Forces Edit…: Opens the external force edit box. This allows the current external force settings to be viewed and edited.

+$#>Menu Tree – Graphics Switches

A menu tree dialog box is available that contains all the graphics menus in one location. This can be used as an alternative to the main toolbar menu entries as it can remain open and allow quicker access to individual switches than is achieved via the main menu.

To open the menu tree use the menu Graphics / Graphics Switches Menu Tree.

{bmc bm178.bmp}
Graphics Switches Menu Tree

The menu tree has the following main branches; Point Nos; Point Labels; Point Values; Part Nos; Part Labels; Part C of G Visibility; Enhanced Visibility; Display Both Sides; Compliance Visibility; Pick Visibility and View Definition Values. Expand the tree branches to find other individual menu switches.

+$#>Menu Tree – Edit Menus

A menu tree dialog box is available that contains all the edit menus in one location. This can be used as an alternative to the main toolbar menu entries as it can remain open and allow quicker access to individual switches than is achieved via the main menu.

To open the menu tree use the menu Edit / Edit Menu Tree.

{bmc bm179.bmp}
Edit Menu Tree

The menu tree has two main branches; Edit and Graphics. Expand the tree branches to find other individual menu switches.

+$#>Icon Description – General

The following icons are used within the application dialogue boxes. A brief description is given for each. The ones shown on your display may differ due to local settings. Users can re-define toolbar icons through the SetUp / Customize Toolbars menu option.

{bmc bm180.bmp} Generic Editor Icon, normally opens standard data editor display.

{bmc bm181.bmp} Opens this Help File at context sensitive page

+$#>Icon Description – File Toolbar

The following icons are displayed on the default File toolbar. A brief description is given for each. The ones shown on your display may differ due to local settings. Users can re-define toolbar icons through the SetUp / Customize Toolbars menu option.

{bmc bm182.bmp} Open existing data file.

{bmc bm183.bmp} Save data to file

{bmc bm184.bmp} Change to 2D module, Bump articulation

{bmc bm185.bmp} Change to 2D module, Roll articulation

{bmc bm186.bmp} Change to 3D module, Bump articulation

{bmc bm187.bmp} Change to 3D module, Roll articulation

{bmc bm188.bmp} Change to 3D module, Steer articulation

{bmc bm189.bmp} Change to move ground plane in bump solver option

{bmc bm190.bmp} Change to move body in bump solver option

{bmc bm191.bmp} Toggle 3D compliant solver setting

{bmc bm192.bmp} Toggle 3D compliance use external forces setting

{bmc bm193.bmp} Toggle Tolerance analysis status

{bmc bm194.bmp} Set to Edit mode

{bmc bm195.bmp} Set to Joggle edit mode

{bmc bm196.bmp} Set to Drag edit mode

+$#>Icon Description – View Toolbar

The following icons are displayed on the view toolbar. A brief description is given for each.
The ones shown on your display may differ due to local settings. Users can re-define toolbar icons through the SetUp / Customize Toolbars menu option.

{bmc bm197.bmp} Toggle dynamic viewing on/off.

{bmc bm198.bmp} Set dynamic view on and mode to translate.

{bmc bm199.bmp} Set dynamic view on and mode to scale.

{bmc bm200.bmp} Set dynamic view on and mode to rotate.

{bmc bm201.bmp} Start zoom event on the graphics display.

{bmc bm202.bmp} Autoscale all open graphs.

{bmc bm203.bmp} Set graphics view style to Wire Frame.

{bmc bm204.bmp} Set graphics view style to Solid Fill.

{bmc bm205.bmp} Set graphics view style to Hidden Line.

{bmc bm206.bmp} Set graphics view style to Depth Buffered (flat shaded).

{bmc bm207.bmp} Set graphics view to Y-Z plane.

{bmc bm208.bmp} Set graphics view to X-Z plane.

{bmc bm209.bmp} Set graphics view to X-Y plane.

{bmc bm210.bmp} Save current graphics view to temporary store.

{bmc bm211.bmp} Cycle though the available tracking options, or the available dynamic view options.

+$#>Icon Description – Graphics Toolbar

The following icons are displayed on the Graphics toolbar. A brief description is given for each.
The ones shown on your display may differ due to local settings. Users can re-define toolbar icons through the SetUp / Customize Toolbars menu option.

{bmc bm212.bmp} Toggles the visibility on the graphics display of the hard point template numbers.

{bmc bm213.bmp} Turns point limits to ‘use’. If the current visibility setting of the limit boxes was ‘off’ they will be turned ‘on’.

{bmc bm214.bmp} Toggles the visibility on the graphics display of the hard point co-ordinates.

{bmc bm215.bmp} Toggles the visibility on the graphics display of the springs’ enhanced graphics.

{bmc bm216.bmp} Toggles the visibility on the graphics display of the dampers’ enhanced graphics.

{bmc bm217.bmp} Toggles the visibility on the graphics display of the wheels’ enhanced graphics.

{bmc bm218.bmp} Toggles the visibility on the graphics display of the pivots’ enhanced graphics.

{bmc bm219.bmp} Toggles the visibility on the graphics display of the grids’ enhanced graphics.

{bmc bm220.bmp} Toggles the visibility on the graphics display of the body’s enhanced graphics. Will only appear if a default body type has been set, (see data menu).

{bmc bm221.bmp} Set the graphics display to show both front and rear axle models, (if loaded).

{bmc bm222.bmp} Sets the graphic display to show the front suspension model only, (note you will not be able to select this option if you only have a rear suspension loaded).

{bmc bm223.bmp} Sets the graphic display to show the rear suspension model only, (note you will not be able to select this option if you only have a front suspension loaded).

{bmc bm224.bmp} Toggles the animation status. Stops or starts the animation of the model over the currently set articulation range.

{bmc bm225.bmp} Toggles the graphics display setting for drawing both suspension sides.

{bmc bm226.bmp} Copies the current graphic display to the Windows® clipboard.

+$#>Icon Description – Graphs + Data Toolbar

The following icons are displayed on the Graphs + Data toolbar. A brief description is given for each. The ones shown on your display may differ due to local settings. Users can re-define toolbar icons through the SetUp / Customize Toolbars menu option.

{bmc bm227.bmp} Open a new results graph.

{bmc bm228.bmp} Autoscales all open graphs.

{bmc bm229.bmp} Opens the model property display. Tree structure based display to access model properties.

{bmc bm230.bmp} Opens the front suspension hard point values for viewing and editing, (not available if only rear suspension loaded).

{bmc bm231.bmp} Opens the rear suspension hard point values for viewing and editing, (not available if only front suspension loaded).

{bmc bm232.bmp} Lists the Parameters data set for viewing and editing.

{bmc bm233.bmp} Lists the Tyre data set values for viewing and editing.

{bmc bm234.bmp} Opens the Suspension Derivative File (SDF). This scrollable textual display lists the an echo of the suspension hard points and incremental listings of the relevant suspension characteristics for all articulation types.

{bmc bm235.bmp} Saves the current suspension hard points to a temporary store, given a unique label for possible later retrieval. This temporary store only exists whilst the application is open such that all saved co-ordinate sets are lost when the application is closed. Any number of sets can be stored.

{bmc bm236.bmp} Cancels the current group selection, returning back to all hard points accessible for individual editing.

{bmc bm237.bmp} Creates an new points group. A new group must be given a unique label to identify it. The number of points required to add to it set and each required point picked from the available suspension end lists.

{bmc bm238.bmp} Runs a utility function that will reset the vehicle model to a new ride height. The value required is a delta from the current position. A positive value lowers the body, i.e. reduces the ride height.

{bmc bm239.bmp} Option to list suspension hard points at a defined bump plus steer position. Define the required bump value, (+ve is in bump) and steer value.

{bmc bm240.bmp} Automatic window positioning option. All open windows are re-sized to a common size and cascaded down from the top left hand corner in regular steps.

{bmc bm241.bmp} Convenience routine to convert existing 2D model data to selected 3D suspension.

+$#>Data Requirements - Introduction

This section describes the data requirements for both the 2D and 3D suspension analysis modules. Each data variable is listed, together with its units and any default value.

The listings are broken down into sections as they are displayed in the interface.

+$#>Data Requirements – Co-ordinate System

The ‘SHARK’ co-ordinate system is a right handed system with the Y-axis across the car track, the origin of which is assumed to be on the vehicle centre line and the +ve direction being towards the offside suspension (Right hand Corner sitting in car). The X-axis is along the vehicle wheelbase, normally with the origin in front of the vehicle with the +ve direction towards the rear. The X-axis only applies to the 3D module, all 2D modes being in the Y-Z or cross car plane. The Z-axis is the vertical height, the origin of which for 2D modes is assumed to be the ground plane, but for the 3D modes can be at any height position. The +ve direction is taken as upwards, (note this co-ordinate system is different to the original UNIX version of SHARK, which had the X and Y axes transposed).

{bmc bm242.bmp}
‘SHARK’ Co-ordinate System

The default mode for a single corner model is to work in the +ve Y axis side, (i.e. hard point y-values are +ve). This default mode can be switched such that the single corner default is for hard points to be in the –ve Y position. To change between these two settings use the toggle check 

+$#>Data Requirements – 2D Data Requirements

The 2D module has some specific requirements for data. It has a reduced set of suspension types when compared to the 3D module, whilst its General data set has variables unique to the 2D module. Some of the General data values are common to both the 2D and 3D modules and will be covered in the description of the 3D data requirements.

+$#>Data Requirements – 2D Suspension Type

The available suspension types for the 2D module are Double Wishbone or Macpherson Strut.

{bmc bm8.bmp}
Setting the 2D Suspension type from the New menu

+$#>Data Requirements – 2D General Data

Vehicle Track,  (real),  (units mm),  (default 1600 mm)
Sets the static vehicle track, the value is the Y-axis distance between the two assumed tyre contact patch centre’s. Must be a positive number

Kingpin Angle,  (real),  (units deg),  (default 10 deg)
Sets the static kingpin angle, being the angle between the upper and lower ball joints in the Y-Z or cross car plane for a double wishbone suspension type, or the angle between the strut top and the lower ball joint, again in the Y-Z plane, for a Macpherson strut suspension. A positive Kingpin angle is taken as when the upper ball joint, (or strut top), is inboard of the lower ball joint, i.e. smaller Y value.

Kingpin Offset at Ground,  (real),  (units mm),  (default 20 mm)
Sets the static Kingpin offset, the offset being the Y-axis or cross car distance between the tyre contact patch centre and the intersection of the kingpin axis with the ground. A positive offset is when the tyre contact patch centre is outboard of the kingpin axis intersection. 

Damper Angle,  (real),  (units deg),  (default 10 deg) {Strut Only}
Sets the static damper angle, being the angle between the strut top and a point on the strut slider axis, in the Y-Z plane. A positive damper angle is taken as when the strut top is inboard of the strut slider point, i.e. smaller Y value.

Camber Change in Bump,  (real),  (deg/mm),  (default -0.04 deg/mm)
This value is used initially to set the user defined camber change line on the camber angle graph over the bump travel region. It is subsequently used to define the required wheel camber angle in bump travel, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in positive camber with positive wheel travel.

Camber Change in Rebound, (real), (deg/mm), (default -0.04 deg/mm)
This value is used initially to set the user defined camber change line on the camber angle graph over the rebound travel region. It is subsequently used to define the required wheel camber angle in rebound travel, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in positive camber with positive wheel travel.

Camber Change in Roll,  (real),  (units deg/mm),  (default 0.5 deg/deg)
This value is used initially to set the user defined camber change line on the camber angle against roll graph. It is subsequently used to define the required wheel camber angle under roll articulation, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in positive camber with a positive roll angle.

Static Roll Centre Height,  (real),  (units mm),  (default 50 mm)
Sets the static roll centre height, this is the distance up the Z-axis from the ground plane to the required static roll centre.

Roll Centre Height Change in Bump, (real), (units mm/mm), (default 1.0 mm/mm)
This value is used initially to set the user defined roll centre height line on the roll centre height graph over the bump travel region. It is subsequently used to define the required roll centre height in bump travel, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in the roll centre height with positive wheel travel.

Roll Centre Height Change in Rebound, (real), (units mm/mm), (def 1.0 mm/mm)
This value is used initially to set the user defined roll centre height line on the roll centre height graph over the rebound travel region. It is subsequently used to define the required roll centre height in rebound travel, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in the roll centre height with positive wheel travel.

Roll Centre Height Change in Roll, (real), (units mm/deg), (default 0.0 mm/mm)
This value is used initially to set the user defined roll centre height line on the roll centre height against roll graph. It is subsequently used to define the required roll centre height in roll articulation, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in roll centre height with a positive roll angle. 

Roll Centre Lateral Change in Roll, (real), (units mm/deg), (default 0.0 mm/mm)
This value is used initially to set the user defined roll centre lateral line on the roll centre lateral against roll graph. It is subsequently used to define the required roll centre lateral position in roll articulation, when a degree of freedom is introduced into the suspension model. A positive value indicates an increase in roll centre lateral Y value with a positive roll angle.

Bump Travel,  (real),  (units mm), (default 60 mm)
Sets the bump travel from static ride, it is the distance in the Z-axis that the ground plane, (or body), is moved through. Must be a positive number.

No. of Bump Solution Steps,  (integer),  (default 4)
Sets the number of solution steps performed between static and full bump travel.

Rebound Travel,  (real),  (units mm), (default 60 mm)
Sets the rebound travel from static ride, it is the distance in the Z-axis that the ground plane, (or body), is moved through. Must be a positive number.

No. of Rebound Solution Steps,  (integer),  (default 4)
Sets the number of solution steps performed between static and full rebound travel.

Roll Travel,  (real),  (units deg), (default 5 deg)
Sets the roll travel from static ride, it is the total angle that the body is rolled about the X-axis. Must be a positive number.

No. of Roll Solution Steps,  (integer),  (default 4)
Sets the number of solution steps performed between static and full roll.

+$#>Data Requirements – 2D Double Wishbone Suspension Hard Points

2D Double Wishbone Suspension Hard Points

Lower Outer Height (Z),  (real),  (units mm),  (default 200 mm)
Defines the static Z height of the lower wishbone outer ball joint, relative to the ground plane.

Upper Outer Height (Z),  (real),  (units mm),  (default 500 mm)
Defines the static Z height of the upper wishbone outer ball joint, relative to the ground plane.

Lower Inner Cross Car (Y),  (real),  (units mm),  (default 248 mm)
Defines the static Y co-ordinate of the lower wishbone inner ball joint, relative to the vehicle centre line. 

Lower Inner Height (Z),  (real),  (units mm),  (default 175 mm)
Defines the static Z height of the lower wishbone inner ball joint, relative to the ground plane.

Upper Inner Cross Car (Y),  (real),  (units mm),  (default 367 mm)
Defines the static Y co-ordinate of the upper wishbone inner ball joint, relative to the vehicle centre line. 

Upper Inner Height (Z),  (real),  (units mm),  (default 426 mm)
Defines the static Z height of the upper wishbone inner ball joint, relative to the ground plane.

(Note: All 2D suspension Z co-ordinates are relative to an assumed zero ground plane, i.e., Z origin is ground plane.)

+$#>Data Requirements – 2D Macpherson Strut Suspension Hard Points

2D Macpherson Strut Suspension Hard Points

Lower Outer Height (Z),  (real),  (units mm),  (default 200 mm)
Defines the static Z height of the lower wishbone outer ball joint, relative to the ground plane.

Strut Top Height (Z),  (real),  (units mm),  (default 500 mm)
Defines the static Z height of the strut top, relative to the ground plane.

Lower Inner Cross Car (Y),  (real),  (units mm),  (default 248 mm)
Defines the static Y co-ordinate of the lower wishbone inner ball joint, relative to the vehicle centre line. 

Lower Inner Height (Z),  (real),  (units mm),  (default 175 mm)
Defines the static Z height of the lower wishbone inner ball joint, relative to the ground plane.

(Note: All 2D suspension Z co-ordinates are relative to an assumed zero ground plane, i.e., Z origin is ground plane.)

+$#>Data Requirements – 3D Data Requirements

The 3D module data requirements are broken down in to sets. Each set is described separately. The data requirements for each of the default suspension template types is listed. Some of the data sets given here apply in part to both the 3D module and the 2D module.

+$#>Data Requirements – 3D Suspension End

Suspension models are defined as being associated to either the ‘Front’ or ‘Read’ end of the vehicle. The allowable suspension templates vary depending on this selection, since front suspension types must be steerable.

Complete vehicle models can be built, (i.e. Front and Rear models), by creating one of each through the ‘new’ menu.

{bmc bm0.bmp}
Selecting the Suspension end and templates from the New display

A suspension end model can also either be a single corner or a full axle. A convenience menu option is provided Edit / Convert Corner to Axle Model that will convert the current template from a corner model to a full axle model that is initially symmetrical. A full axle mode that is marked as symmetric will continue to be symmetric on subsequent hard point changes through the template identifying opposite points as linked. This linking is broken if the suspension symmetry flag is changed to asymmetric at the top of the ‘File/New’ dialogue box.

+$#>Data Requirements – 3D Suspension Type

3D Suspension Type

Since users can create/delete and include their own templates the lists given here may not be the same as displayed. The presented lists represent the ‘standard’ templates that are ‘hard-coded’  into the as-shipped application.

For front suspension’s
	Select From:	
				Type 1    Double wishbone, damper to lower wishbone.
		             	Type 3    Steerable Macpherson strut.
		             	Type 6    Double Wishbone, damper to upper wishbone.
		             	Type 12  Steerable twin parallel wishbones + knuckle.
		             	Type 13  Double Wishbone, damper to knuckle.
		             	Type 14  Double wishbone, push rod to damper.
		             	Type 15  Double wishbone, rocker arm damper.
		             	Type 17  Double wishbone, pushrod monoshock.
		             	Type 18  Double wishbone, upper toe link + ‘S’ link.
				Type 20  Double wishbone, twin outer ball joints.
				Type 22  Double wishbone, twin outer ball joints spring front.
				Type 23  Double wishbone, anti roll bar
				Type 24  Steerable Macpherson Strut, twin outer ball joints.
				Type 25  Double wishbone, twin lower outer ball joints.
				Type 26  Double wishbone, compliant rack, damper to lower.
				Type 27  Steerable Macpherson Strut, twin lower link.

For rear suspension’s
	Select From:	
				Type 1    Double wishbone, damper to lower wishbone.
		             	Type 2    ‘H’ frame lower, single upper link.
		             	Type 3    Steerable Macpherson strut.
		             	Type 4    Non-Steerable Mac strut, twin lower link.
		             	Type 5    5-Link Rigid Axle, (Panhard Rod).
		             	Type 6    Double Wishbone, damper to upper wishbone.
		             	Type 7    Non-Steerable Mac strut, toe link to wishbone.
		             	Type 8    4-Link Rigid Axle, (Panhard Rod).
		             	Type 9    4-Link Rigid Axle, (twin upper).
		             	Type 10  Trailing arm, upper and lower rear links.
		             	Type 11  Semi trailing arm.
		             	Type 12  Steerable twin parallel wishbones + knuckle.
		             	Type 13  Double Wishbone, damper to knuckle.
		             	Type 14  Double wishbone, push rod to damper.
		             	Type 15  Double wishbone, rocker arm damper.
		             	Type 16  Non-Steerable lower ‘A’ with toe link.
		             	Type 17  Double wishbone, pushrod monoshock.
		             	Type 18  Double wishbone, upper toe link + ‘S’ link.
		             	Type 19  Hinged Trailing Arm, Twin Lower Link.
		             	Type 20  Double Wishbone, twin outer ball joints.
		             	Type 21  5-Link Rigid Axle, (Watts Linkage).
		             	Type 22  Double Wishbone, Twin outer ball joints, Spring front.
		             	Type 23  Double Wishbone, anti roll bar. 
		             	Type 24  Steerable Macpherson Strut, twin outer ball joints.
		             	Type 25  Double Wishbone, Twin Lower Outer ball joints.
		             	Type 26  Double Wishbone, compliant rack, damper to lower.
		             	Type 27  Steerable Mcpherson Strut, twin lower link.
		             	Type 28  4-Link Rear, transverse control link.
		             	Type 29  Twist Beam – twin Wheel.
		             	Type 30  Generic 5-link Rear.

{bmc bm9.bmp}
Selecting the Front Suspension template from the New display

+$#>Data Requirements – 3D General Data (Parameters)

3D General Data

Bump Travel,  (real),  (units mm), (default 60 mm)
Sets the bump travel from static ride, it is the distance in the Z-axis that the ground plane, (or body), is moved through. Must be a positive number. Note that the bump and rebound travel values would normally define an even increment bounded articulation definition. This can be changed to a step-by-step definition sequence similar to that used for the combined mode but with out any steering input. This is enabled/edited through the Data / Use Extended Bump Travel and Data / Edit Extended Bump Travel menu options.

Rebound Travel,  (real),  (units mm), (default 60 mm)
Sets the rebound travel from static ride, it is the distance in the Z-axis that the ground plane, (or body), is moved through. Must be a positive number. See also bump travel above with regard to extended bump travel option.

Bump/Rebound Increment,  (real),  (units mm),  (default 5 mm)
Set the solution step size in bump and rebound when animating or listing SDF’s. See also bump travel above with regard to extended bump travel option. The alternative solver motion option of  ‘Solve by No of Steps’ can be used to directly set the number of steps to reach the maximum travel, (i.e. calculate the increment rather than define it).

Roll Angle,  (real),  (units deg), (default 3 deg)
Sets the roll travel from static ride, it is the total angle that the body is rolled about the Y-axis. Must be a positive number.

Roll Increment,  (real),  (units deg),  (default 0.25 deg)
Sets the solution step size in roll when animating or listing SDF’s.

Steer Travel,  (real),  (units mm),  (default 30.0 mm)
Sets the limit of steering travel for the inner ball joint in the X-axis or cross car direction.

Steer Increment,  (real),  (units mm),  (default 2.0 mm)
Sets the solution step size in steering when animating or listing SDF’s.

Wheelbase,  (real),  (units mm),  (default 2240 mm)
Sets the static vehicle wheelbase, the value is the Y-axis distance between the front and rear wheel centre’s. Must be a positive number.

C of G Height,  (real),  (units mm),  (default 60 mm)
Sets the static centre of gravity height, the distance in the Z-axis of the C of G from the ground plane.

Breaking On Front,  (real),  (units %),  (default 60 %)
Defines the brake split between the front and rear axles, by defining the % braking effort on the front axle.

Drive On Front,  (real),  (units %),  (default 0 %)
Defines the drive split between the front and rear axles, by defining the % drive to the front axle. Thus a rear wheel drive car has a value of 0%, whilst a front wheel drive car has a value of 100%.

Total Weight On Front,  (real),  (units %),  (default 40 %)
Defines the weight split between the front and rear axles, by defining the % weight on the front axle.

Front Brake Type,  (integer),  (default 2)
Defines the brake type for the front suspension as either inboard (1), or outboard (2).

Rear Brake Type,  (integer),  (default 2)
Defines the brake type for the rear suspension as either inboard (1), or outboard (2).

Total Sprung Weight,  (real), (units kg) (default 0.0)
Defines the total sprung weight of the vehicle, (sum of front and rear).

Front Suspension Type,  (integer),  (default 1)
Defines the suspension type for the front suspension as either independent (1), or rigid (2).

Rear Suspension Type,  (integer),  (default 1)
Defines the suspension type for the rear suspension as either independent (1), or rigid (2).

Drive Shaft Joint Radius,  (real),  (units mm),  (default 65.0)
Defines the Joint radius used for the drive shaft joints. This is available as a variable for use in User SDF calculations.

No of Bump Increments,  (integer),  (default 5)
Is optionally used to define the number of bump increments taken to reach the defined maximum bump travel limit. Only applies when the solver motion option is set to ‘Solve by No of Steps’.

No of Rebound Increments,  (integer),  (default 5)
Is optionally used to define the number of rebound increments taken to reach the defined maximum rebound travel limit. Only applies when the solver motion option is set to ‘Solve by No of Steps’.

No of Roll Increments,  (integer),  (default 5)
Is optionally used to define the number of roll increments taken to reach the defined maximum roll travel limit. Only applies when the solver motion option is set to ‘Solve by No of Steps’.

No of Steer Increments,  (integer),  (default 5)
Is optionally used to define the number of steer increments taken to reach the defined maximum steering travel limit. Only applies when the solver motion option is set to ‘Solve by No of Steps’.

{bmc bm243.bmp}
Editing the Parameters (General Data) data set

+$#>Data Requirements – 3D Body Type

The 3D body type is a menu selection rather than a data variable. The menu choices are;

	None
	Saloon
	Open Sports
	Old Single Seater
	Single Seater
	Utility
	Super Saloon
	Mini Van
	User Defined

{bmc bm244.bmp}
Example Graphics – Open Sports Body Type Shown

For the user defined body it is possible to define the body graphics as a combination of 3d vectors and 3d facets. To edit the user defined body data select the menu option Data / Edit User Body Data… The displayed spread-sheet has two paneled tabs. The first is for 3d vectors, where each vector requires a start point and an end point. The second tab is for 3d facets where each facet can be a ‘n’ noded planar facet. Each node of the facet requires an x, y and z co-ordinate.

The body data can be populated with one of the standard types to act as a start point. Use the local File / Load Standard body Data menus to do this.

Body facet data can also be imported from an external STL file. Scaling and shift options are offered to manipulate the imported STL facets.

The application is currently restricted to a maximum of 10 noded facets and a total of 2000 facets and 800 vectors.

To edit user defined body data, open using Data / Edit User Body Data, if this menu is un-selectable you first need to set body type to user defined, (Data / Body Type / User Defined). The data edit display list vectors and facets separately.

{bmc bm245.bmp}
Editing User Body Data - Vectors

For each vector define the start and end co-ordinates as a global (x, y, z) value.

For each facet define as many point co-ordinates triplets as required. A minimum of three points is required for a facet. These point co-ordinates should be in the global axis system.

+$#>Data Requirements – 3D Tyre Data

The 2D module has some specific requirements for data.

Rolling Radius,  (real),  (units mm),  (default 225 mm)
Sets the relevant tyres rolling radius.

Tyre Width,  (real),  (units mm),  (default 150 mm)
Sets the relevant tyre width, used to support graphical display only.

Vertical Stiffness,  (real),  (units N/mm),  (default 400 N/mm)
Sets the relevant tyres vertical stiffness, used in the compliance analysis.

Spring Diameter,  (real),  (units mm),  (default 14 mm)
Sets the diameter of the graphical spring used to optionally represent the tyre vertical spring.

Other related graphical items such as colour can also be edited through this display.

Enhanced Tyre and Spring

The graphical representation of the tyre and wheel can be extended beyond the default. The user can define a cross section that is then revolved around the spindle axis. These user profiles can thus include much more surface definition than the simple models.

{bmc bm246.bmp}
Editing the Tyre data set

+$#>Data Requirements – 3D Steering Type

The 3D steering type is a menu selection rather than a data variable. The menu choices are;

	Steering Rack
	Steering Box

{bmc bm11.bmp}
Setting the Steering type from the ‘New’ menu

The steering box option requires additional data hard points to be defined:

Point 101:  	1st Point on Box Axis, x,y,z (mm).
Point 102:  	2nd Point on Box Axis, x,y,z (mm).
Point 103:  	Pitman Joint, x,y,z (mm).

{bmc bm247.bmp}
Editing the Steering Box Hard Point Data

The steering box hard points can be optionally asymmetric.

+$#>Data Requirements – 3D Comments

The data for the title block is intended for use as a labelling/description mechanism. This optional data block is only accessible via the Data / Model Comments… menu item.

{bmc bm248.bmp}
Editing the comments section

+$#>Data Requirements – 3D Bush Properties

The Bush Properties data is displayed by hard point and is added to the bottom of the normal points’ position edit box when in compliant mode. A bush has a local co-ordinate system defined relative to the global Cartesian set. The bushes stiffness properties are then defined in this local co-ordinate system.

The individual data fields are:

Point on Bush local Z-Axis, X, Y and Z, Abs,  (real),  (units mm),  (default none)
Sets the position of a point on the local Z-axis for the current hard points bush local axes, (local axis origin is the current points kinematic position). This definition is in absolute x, y and z co-ordinates, (‘absolute’ implies relative to global Cartesian origin).

Point on Bush local Z-Axis, X, Y and Z, Rel,  (real),  (units mm),  (default none)
Sets the position of a point on the local Z-axis for the current hard points bush local axes, (local axis origin is the current points kinematic position). This definition is in relative x, y and z co-ordinates, (‘relative’ implies relative to selected hard points’ position).

Point on Bush local Z-Axis, Pnt,  (choice),  (default none)
Sets the position of a point on the local Z-axis for the current hard points bush local axes, (local axis origin is the current points kinematic position). This definition is by selecting another hard point in the suspension model. Typical use of this would be in aligning a bush axis along a wishbone axis by pointing towards the second point on the pivot axis.

Point in Bush local X-Z Plane, X, Y and Z, Abs,  (real),  (units mm),  (default none)
Sets the position of a point on the local X-Z plane for the current hard points bush local axes,  (local axis origin is the current points kinematic position). This definition is in absolute x, y and z co-ordinates, (‘absolute’ implies relative to global Cartesian origin).

Point on Bush local X-Z Plane, X, Y and Z, Rel,  (real),  (units mm),  (default none)
Sets the position of a point on the local X-Z plane for the current hard points bush local axes,  (local axis origin is the current points kinematic position). This definition is in relative x, y and z co-ordinates, (‘relative’ implies relative to selected hard points’ position).

Bush Local Stiffness, X, Y and Z,  (real),  (units N/mm),  (default 1000 N/mm or 2000 N/mm)
Sets the translational stiffness of the current bush in the defined local axes.

Bush Local Stiffness, X-X, Y-Y and Z-Z,  (real),  (units N.m/Rad),  (default 0 N.m/Rad)
Sets the rotational stiffness of the current bush in the defined local axes.

Bush Local Damping (Loss Angle), X, Y and Z,  (real),  (units Deg),  (default 3.0 Deg)
Sets the translational damping of the current bush in the defined local axes. Note that the damping is defined in terms of a loss angle rather than an absolute damping value. Such that damping is applied to the model as either, Stiffness x Cos(loss angle) or Stiffness x Sin(loss angle) for the real and imaginary parts of the solution.

Bush Local Damping (Loss Angle), X-X, Y-Y- and Z-Z,  (real),  (units Deg),  (default 0.0 Deg)
Sets the rotational damping of the current bush in the defined local axes. Note that the damping is defined in terms of a loss angle rather than an absolute damping value. Such that damping is applied to the model as either, Stiffness x Cos(loss angle) or Stiffness x Sin(loss angle) for the real and imaginary parts of the solution.

{bmc bm249.bmp}
Bush Properties – Example Compliant Data

The bush edit dialog box attempts to stop invalid bush axes definitions. These normally occur when the z-axis point and the point in the x-y plane are the same or are along the same vector. Typical examples of these occur with the compliant rack models when the z-axis point is aligned relative to the other rack bush but the x-y point has not been changed from the default.

The inclusion of a compliant racks bush also normally requires that the rotational stiffness values are defined for the rack bushes to control the rack rotations.

+$#>Data Requirements – 3D External Force Data

The External Force data is displayed by ‘Set’. Each set is a collection of forces, each force having a definition in terms of its head and tail positions, attachment part and magnitude. Force head and tail positions are defined in either absolute position or relative to a hard point position.

The individual data fields are:

Description,  (string),  (units none),  (default none)
Label for the force set.

End,  (selection),  (units none),  (default none)
Identifies which suspension corner to apply the force too.

Apply to Part,  (selection),  (units none),  (default none)
Identifies which part in the selected corners’ suspension to apply the force too.

Magnitude,  (real),  (units N),  (default 0 N)
Defines the magnitude of the force. A force can be fixed or variable. Changing the setting from a single ‘fixed’ value to a ‘variable’ force enables an edit box for the variable force. The force can then be defined on a by increment variation.

Phase,  (real),  (units deg),  (default 0 deg)
Defines the phase of a force. It is only relevant for a Forced/Damped analysis.

Force Head, X, Y and Z, Abs,  (real),  (units mm),  (default none)
Sets the position of the force head in the global Cartesian co-ordinate system, co-ordinate system origin taken as global co-ordinate system origin.

Force Head, X, Y and Z, Rel. to Pnt.,  (real),  (units mm),  (default none)
Sets the position of the force head in the global Cartesian co-ordinate system, co-ordinate system origin taken as selected hard point.

Force Tail, X, Y and Z, Abs,  (real),  (units mm),  (default none)
Sets the position of the force tail in the global Cartesian co-ordinate system, co-ordinate system origin taken as global co-orindate system origin.

Force Tail, X, Y and Z, Rel. to Pnt.,  (real),  (units mm),  (default none)
Sets the position of the force tail in the global Cartesian co-ordinate system, co-ordinate system origin taken as selected hard point.

Force Tail, X, Y and Z, Rel. to Head,  (real),  (units mm),  (default none)
Sets the position of the force tail in the global Cartesian co-ordinate system, co-ordinate system origin taken as the ‘head’ of the current force.

{bmc bm250.bmp}
External Forces Properties – Example Data

Also displayed on this display are solver switch settings for the Suspension Spring Pre-load force, Drive shaft Loads and Braked Hub. These provide access to the ‘by force set’ solver switch settings for these load cases.

The Braked Hub allows the user to select if the longitudinal wheel/hub loads are to be reacted by the brake and hence to load the upright or if these loads are to reacted by the drive shaft. This enables both braking and drive load case sets to be assembled.

+$#>Data Requirements – 3D Part C of G Properties

The C of G Properties data is displayed by part. Each part optionally has a point attached to it that is identified as the C of G point. If a template does not have an associated C of G point either an existing point can be flagged as the C of G by editing the template, or a new point can be added to the template via the Edit / Add to Model / Part C of Gs menu options. A point added to the template in this way is automatically flagged as being a C of G point. C of G points are only visible when in compliant mode and are drawn as a green and black quadrant symbol. An additional set of visibility switches are used for C of G points that control point visibility, axis marker points and axes. Older model files will not have C of G points in them and will need modifying to match the updated templates.

{bmc bm251.bmp}
C of G Marker Point – Screen Shot

Part mass properties enable modal frequencies and forced-damped responses to be identified.

The individual data fields are:

Point Label,  (string),  (default none)
Sets a string label for each point.

Kinematic Point Coordinates (Global),  (real),  (unit mm),  (default none)
Lists the current kinematic hard point co-ordinates.

Point on C of G local Z-Axis, X, Y and Z, Abs,  (real),  (units mm),  (default none)
Sets the position of a point on the local Z-axis for the current hard points C of G local axes, (local axis origin is the current points kinematic position). This definition is in absolute x, y and z co-ordinates, (‘absolute’ implies relative to global Cartesian origin).

Point on C of G local Z-Axis, X, Y and Z, Rel,  (real),  (units mm),  (default none)
Sets the position of a point on the local Z-axis for the current hard points C of G local axes, (local axis origin is the current points kinematic position). This definition is in relative x, y and z co-ordinates, (‘relative’ implies relative to selected hard points’ position).

Point on C of G local Z-Axis, Pnt,  (choice),  (default none)
Sets the position of a point on the local Z-axis for the current hard points bush local axes, (local axis origin is the current points kinematic position). This definition is by selecting another hard point in the suspension model. Typical use of this would be in aligning a bush axis along a wishbone axis by pointing towards the second point on the pivot axis.

Point in C of G local X-Z Plane, X, Y and Z, Abs,  (real),  (units mm),  (default none)
Sets the position of a point on the local X-Z plane for the current hard points C of G local axes,  (local axis origin is the current points kinematic position). This definition is in absolute x, y and z co-ordinates, (‘absolute’ implies relative to global Cartesian origin).

Point in C of G local X-Z Plane, X, Y and Z, Rel,  (real),  (units mm),  (default none)
Sets the position of a point on the local X-Z plane for the current hard points C of G local axes,  (local axis origin is the current points kinematic position). This definition is in relative x, y and z co-ordinates, (‘relative’ implies relative to selected hard points’ position).

C of G Mass,  (real),  (units Kg),  (default 1.0 Kg)
Sets the mass of the part that this point is the C of G marker for.

C of G Local Inertia, Ixx, Iyy, Izz, Ixy, Ixz and Iyz,  (real),  (units kg/mm2)
Sets the 6 inertia values for the part. Inertia properties are defined about the local axis system that has been defined by the points above.

{bmc bm252.bmp}
C of G Properties – Example Data

+$#>Data Requirements – Type 1: Double Wishbone, Damper to Lower Wishbone

Type 1    Double wishbone, damper to lower wishbone.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G

{bmc bm253.bmp}

Suspension Type 1, LSA Screen Shot – Default Co-ordinates
{bmc bm254.bmp}
Suspension Type 1, Schematic

+$#>Data Requirements – Type 2: ‘H’ Frame Lower, Single Upper Link

Type 2    ‘H’ frame lower, single upper link.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer front pivot point, x,y,z (mm).
Point 4:  	Lower wishbone outer rear pivot point, x,y,z (mm).
Point 5: 	Upper link inner ball joint, x,y,z (mm).
Point 6:		Upper link outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Upper spring pivot point, x,y,z (mm).
Point 10:	Lower spring pivot point, x,y,z (mm).
Point 11:	Wheel spindle point, x,y,z (mm).
Point 12:	Wheel centre point, x,y,z (mm).

Point 13:	Part 1 C of G
Point 14:	Part 2 C of G
Point 15:	Part 3 C of G

{bmc bm255.bmp}
Suspension Type 2, LSA Screen Shot – Default Co-ordinates
{bmc bm256.bmp}
Suspension Type 2, Schematic

+$#>Data Requirements – Type 3: Steerable Macpherson Strut

Type 3    Steerable Macpherson strut.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4: 	Strut slider axis point, x,y,z (mm).
Point 5:		Strut top point, x,y,z (mm).
Point 6:		Outer track rod ball joint, x,y,z (mm).
Point 7:		Inner track rod ball joint, x,y,z (mm).
Point 8:		Upper spring pivot point, x,y,z (mm).
Point 9:		Lower spring pivot point, x,y,z (mm).
Point 10:	Wheel spindle point, x,y,z (mm).
Point 11:	Wheel centre point, x,y,z (mm).

Point 12:	Part 1 C of G
Point 13:	Part 2 C of G
Point 14:	Part 3 C of G
Point 15:	Part 4 C of G

{bmc bm257.bmp}
Suspension Type 3, LSA Screen Shot – Default Co-ordinates
{bmc bm258.bmp}
Suspension Type 3, Schematic

+$#>Data Requirements – Type 4: Non-Steerable Macpherson Strut, Twin Lower Link

Type 4    Non-Steerable Mac strut, twin lower link.

Point 1:  	Front lower link inboard, x,y,z (mm).
Point 2:  	Rear lower link inboard, x,y,z (mm).
Point 3:  	Front lower link outboard, x,y,z (mm).
Point 4:  	Rear lower link outboard, x,y,z (mm).
Point 5: 	Strut slider axis point, x,y,z (mm).
Point 6:		Strut top point, x,y,z (mm).
Point 7:		Reaction rod outboard point, x,y,z (mm).
Point 8:		Reaction rod body point, x,y,z (mm).
Point 9:		Spring top centre line, x,y,z (mm).
Point 10:	Spring bottom at centre line, x,y,z (mm).
Point 11:	Wheel spindle point, x,y,z (mm).
Point 12:	Wheel centre point, x,y,z (mm).

Point 13:	Part 1 C of G
Point 14:	Part 2 C of G
Point 15:	Part 3 C of G
Point 16:	Part 4 C of G
Point 17:	Part 5 C of G

{bmc bm259.bmp}
Suspension Type 4, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 5: 5-Link Rigid Axle (Panhard Rod)

Type 5    5-Link Rigid Axle (Panhard Rod).

Point 1:  	Right lower link body end, x,y,z (mm).
Point 2:  	Right upper link body end, x,y,z (mm).
Point 3:  	Left lower link body end, x,y,z (mm).
Point 4:  	Left upper link body end, x,y,z (mm).
Point 5: 	Right lower link axle end, x,y,z (mm).
Point 6:		Right upper link axle end, x,y,z (mm).
Point 7:	 	Left lower link axle end, x,y,z (mm).
Point 8:		Left upper link axle end, x,y,z (mm).
Point 9:		Panhard rod body end, x,y,z (mm).
Point 10:	Panhard rod axle end, x,y,z (mm).
Point 11:	Right spring/damper axle, x,y,z (mm).
Point 12:	Right spring/damper body, x,y,z (mm).
Point 13:	Left spring/damper axle, x,y,z (mm).
Point 14:	Left spring/damper body, x,y,z (mm).
Point 15:	Centre pivot point, x,y,z (mm).
Point 16:	Right wheel centre, x,y,z (mm).
Point 17:	Left wheel centre, x,y,z (mm).
Point 18:	Wheel stub axle point, x,y,z (mm).

Point 19:	Part 1 C of G
Point 20:	Part 2 C of G
Point 21:	Part 3 C of G
Point 22:	Part 4 C of G
Point 23:	Part 5 C of G
Point 24:	Part 6 C of G
Point 25:	Part 7 C of G

{bmc bm260.bmp}
Suspension Type 5, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 6: Double Wishbone, Damper to Upper Wishbone

Type 6    Double Wishbone, damper to upper wishbone.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G

{bmc bm261.bmp}
Suspension Type 6, LSA Screen Shot – Default Co-ordinates
{bmc bm262.bmp}
Suspension Type 6, Schematic

+$#>Data Requirements – Type 7: Non-Steerable Macpherson Strut, Toe Link to Wishbone

Type 7    Non-Steerable Mac strut, toe link to wishbone.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4: 	Strut slider axis point, x,y,z (mm).
Point 5:		Strut top point, x,y,z (mm).
Point 6:		Outer track rod ball joint, x,y,z (mm).
Point 7:		Steering link to wishbone ball joint, x,y,z (mm).
Point 8:		Upper spring pivot point, x,y,z (mm).
Point 9:		Lower spring pivot point on lower arm, x,y,z (mm).
Point 10:	Wheel spindle point, x,y,z (mm).
Point 11:	Wheel centre point, x,y,z (mm).

{bmc bm263.bmp}
Suspension Type 7, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 8: 4-Link Rigid Axle (Panhard Road)

Type 8    4-Link Rigid Axle, (Panhard rod).

Point 1:  	Right lower link body end, x,y,z (mm).
Point 2:  	Upper link body end, x,y,z (mm).
Point 3:  	Left lower link body end, x,y,z (mm).
Point 4:  	Right lower link axle end, x,y,z (mm).
Point 5: 	Left lower link axle end, x,y,z (mm).
Point 6:		Panhard rod body end, x,y,z (mm).
Point 7:		Panhard rod axle end, x,y,z (mm).
Point 8:		Right spring/damper axle, x,y,z (mm).
Point 9:		Right spring/damper body, x,y,z (mm).
Point 10:	Left spring/damper axle, x,y,z (mm).
Point 11:	Right spring/damper body, x,y,z (mm).
Point 12:	Axle tube – stub axle, x,y,z (mm).
Point 13:	Right wheel centre, x,y,z (mm).
Point 14:	Left wheel centre, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G
Point 19:	Part 5 C of G

{bmc bm264.bmp}
Suspension Type 8, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 9: 4-Link Rigid Axle (Twin Upper)

Type 9    4-Link Rigid Axle (Twin Upper)

Point 1:  	Right lower link body end, x,y,z (mm).
Point 2:  	Right upper link body end, x,y,z (mm).
Point 3:  	Left lower link body end, x,y,z (mm).
Point 4:  	Right lower link axle end, x,y,z (mm).
Point 5: 	Right upper link axle end, x,y,z (mm).
Point 6:		Left lower link axle end, x,y,z (mm).
Point 7:		Left upper link body end, x,y,z (mm).
Point 8:		Left upper link axle end, x,y,z (mm).
Point 9:		Right spring/damper axle, x,y,z (mm).
Point 10:	Right spring/damper body, x,y,z (mm).
Point 11:	Left spring/damper axle, x,y,z (mm).
Point 12:	Left spring/damper body, x,y,z (mm).
Point 13:	Axle tube - stub axle, x,y,z (mm).
Point 14:	Right wheel centre, x,y,z (mm).
Point 15:	Left wheel centre, x,y,z (mm).

Point 16:	Part 1 C of G
Point 17:	Part 2 C of G
Point 18:	Part 3 C of G
Point 19:	Part 4 C of G
Point 20:	Part 5 C of G

{bmc bm265.bmp}
Suspension Type 9, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 10: Trailing Arm, Upper and Lower Rear Links

Type 10  Trailing arm, upper and lower rear links.

Point 1:  	Trailing arm front pivot, x,y,z (mm).
Point 2:  	Lower link inner ball joint, x,y,z (mm).
Point 3:  	Lower link outer ball joint, x,y,z (mm).
Point 4:  	Upper link inner ball joint, x,y,z (mm).
Point 5:		Upper link outer ball joint, x,y,z (mm).
Point 6:		Damper lower trailing arm end, x,y,z (mm).
Point 7: 	Damper body end, x,y,z (mm).
Point 8:		Upper spring pivot point, x,y,z (mm).
Point 9:		Spring lower trailing arm end, x,y,z (mm).
Point 10:	Wheel spindle point, x,y,z (mm).
Point 11:	Wheel centre point, x,y,z (mm).

Point 12:	Part 1 C of G
Point 13:	Part 2 C of G
Point 14:	Part 3 C of G

{bmc bm266.bmp}
Suspension Type 10, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 11: Semi Trailing Arm

Type 11  Semi trailing arm.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:		Damper lower trailing arm end, x,y,z (mm).
Point 4: 	Damper body end, x,y,z (mm).
Point 5:		Upper spring pivot point, x,y,z (mm).
Point 6:		Lower spring pivot point, x,y,z (mm).
Point 7:		Wheel spindle point, x,y,z (mm).
Point 8:		Wheel centre point, x,y,z (mm).

Point 9:		Part 1 C of G

{bmc bm267.bmp}
Suspension Type 11, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 12: Steerable Twin Parallel Wishbones and Knuckle

Type 12  Steerable twin parallel wishbones + knuckle.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Knuckle centre, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Knuckle upper axis point, x,y,z (mm).
Point 16:	Knuckle lower axis point, x,y,z (mm).
Point 17:	Axis point, x,y,z (mm)

Point 18:	Part 1 C of G
Point 19:	Part 2 C of G
Point 20:	Part 3 C of G
Point 21:	Part 4 C of G
Point 22:	Part 5 C of G

{bmc bm268.bmp}
Suspension Type 12, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 13: Double Wishbone Damper to Knuckle

Type 13  Double Wishbone Damper to knuckle.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G

{bmc bm269.bmp}
Suspension Type 13 LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 14: Double Wishbone, Push Rod to Damper

Type 14  Double wishbone, push rod to damper.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Push rod wishbone end, x,y,z (mm).
Point 8: 	Push rod rocker end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Damper to body point, x,y,z (mm).
Point 12:	Damper to rocker point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Rocker axis 1st point, x,y,z (mm).
Point 16:	Rocker axis 2nd point, x,y,z (mm).

Point 17:	Part 1 C of G
Point 18:	Part 2 C of G
Point 19:	Part 3 C of G
Point 20:	Part 4 C of G
Point 21:	Part 5 C of G
Point 22:	Part 6 C of G

{bmc bm270.bmp}
Suspension Type 14, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 15: Double Wishbone, Rocker Arm Damper

Type 15  Double wishbone, rocker arm damper.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Push rod wishbone end, x,y,z (mm).
Point 8: 	Push rod rocker end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Damper to body point, x,y,z (mm).
Point 12:	Damper to rocker point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Rocker axis 1st point, x,y,z (mm).
Point 16:	Rocker axis 2nd point, x,y,z (mm).

Point 17:	Part 1 C of G
Point 18:	Part 2 C of G
Point 19:	Part 3 C of G
Point 20:	Part 4 C of G
Point 21:	Part 5 C of G
Point 22:	Part 6 C of G

{bmc bm271.bmp}
Suspension Type 15, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 16: Non-Steerable Lower ‘A’ with Toe Link

Type 16  Non-Steerable lower ‘A’ with toe link.

Point 1:  	Upper wishbone front pivot, x,y,z (mm).
Point 2:  	Upper wishbone rear pivot, x,y,z (mm).
Point 3:  	Upper wishbone outer ball joint, x,y,z (mm).
Point 4:  	Front lower link outboard, x,y,z (mm).
Point 5: 	Lower link inboard ball joint, x,y,z (mm).
Point 6:		Rear lower link outboard, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Reaction rod outboard point, x,y,z (mm).
Point 10:	Reaction rod body point, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G

{bmc bm272.bmp}
Suspension Type 16, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 17:  Double Wishbone, Push Rod Monoshock

Type 17  Double wishbone, pushrod monoshock.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Push rod wishbone end, x,y,z (mm).
Point 8: 	Push rod rocker end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Damper to body point, x,y,z (mm).
Point 12:	Damper to rocker point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Rocker axis 1st point, x,y,z (mm).
Point 16:	Rocker axis 2nd point, x,y,z (mm).
Point 17:	2nd link 1st rocker end, x,y,z (mm).
Point 18:	2nd link damper rocker end, x,y,z (mm).
Point 19:	Damper rocker axis 1st point, x,y,z (mm).
Point 20:	Damper rocker axis 2nd point, x,y,z (mm).

Point 21:	Part 1 C of G
Point 22:	Part 2 C of G
Point 23:	Part 3 C of G
Point 24:	Part 4 C of G
Point 25:	Part 5 C of G
Point 26:	Part 6 C of G
Point 27:	Part 7 C of G
Point 28:	Part 8 C of G

{bmc bm273.bmp}
Suspension Type 17, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 18: Double Wishbone, Upper Toe Link and ‘S’ Link

Type 18  Double wishbone, upper toe link + ‘S’ link.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Upper toe link inboard end, x,y,z (mm).
Point 16:	Upper toe link outboard end, x,y,z (mm).
Point 17:	Drop link axis point, x,y,z (mm).

Point 18:	Part 1 C of G
Point 19:	Part 2 C of G
Point 20:	Part 3 C of G
Point 21:	Part 4 C of G
Point 22:	Part 5 C of G
Point 23:	Part 6 C of G

{bmc bm274.bmp}
Suspension Type 18, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 19: Hinged Trailing Arm, Twin Lower Link

Type 19  Hinged Trailing Arm, Twin Lower Link.

Point 1:  	Lower front link inboard pivot, x,y,z (mm).
Point 2:  	Lower rear link inboard pivot, x,y,z (mm).
Point 3:  	Lower front link outboard pivot, x,y,z (mm).
Point 4:  	Lower rear link outboard pivot, x,y,z (mm).
Point 5:  	Upper link inboard end, x,y,z (mm).
Point 6:		Upper link outboard end, x,y,z (mm).
Point 7:		Spring/Damper wishbone end, x,y,z (mm).
Point 8:		Spring/Damper body end, x,y,z (mm).
Point 9:		Trailing arm hinge upper joint, x,y,z (mm).
Point 10:	Trailing arm to body, x,y,z (mm).
Point 11:	Wheel spindle point, x,y,z (mm).
Point 12:	Wheel centre point, x,y,z (mm).
Point 13:	Trailing arm hinge lower pivot, x,y,z (mm).

Point 14:	Part 1 C of G
Point 15:	Part 2 C of G
Point 16:	Part 3 C of G
Point 17:	Part 4 C of G
Point 18:	Part 5 C of G

{bmc bm275.bmp}
Suspension Type 19, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 20: Double Wishbone, Twin outer Ball Joints

Type 20  Double Wishbone, Twin Outer Ball Joints.

Point 1:  	Lower wishbone front link inboard pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear link inboard pivot, x,y,z (mm).
Point 3:  	Lower wishbone front link outboard pivot, x,y,z (mm).
Point 4:  	Upper wishbone front link inboard pivot, x,y,z (mm).
Point 5:  	Upper wishbone rear link inboard pivot, x,y,z (mm).
Point 6:  	Upper wishbone front link outboard end, x,y,z (mm).
Point 7:  	Damper wishbone end, x,y,z (mm).
Point 8:  	Damper body end, x,y,z (mm).
Point 9:  	Outer track rod ball joint, x,y,z (mm).
Point 10:  	Inner track rod ball joint, x,y,z (mm).
Point 11:  	Upper Spring pivot point, x,y,z (mm).
Point 12:  	Lower spring pivot point, (to front lower link), x,y,z (mm).
Point 13:  	Wheel spindle point, x,y,z (mm).
Point 14:  	Wheel centre point, x,y,z (mm).
Point 15:  	Lower wishbone rear link outboard pivot, x,y,z (mm).
Point 16:  	Upper wishbone rear link outboard pivot, x,y,z (mm).

Point 17:	Part 1 C of G
Point 18:	Part 2 C of G
Point 19:	Part 3 C of G
Point 20:	Part 4 C of G
Point 21:	Part 5 C of G
Point 22:	Part 6 C of G

{bmc bm276.bmp}
Suspension Type 20, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 21: 5-Link Rigid Axle (Watts Linkage)

Type 21    5-Link Rigid Axle (Watts Linkage).

Point 1:  	Right lower link body end, x,y,z (mm).
Point 2:  	Right upper link body end, x,y,z (mm).
Point 3:  	Left lower link body end, x,y,z (mm).
Point 4:  	Left upper link body end, x,y,z (mm).
Point 5:  	Right lower link axle end, x,y,z (mm).
Point 6: 	Right upper link axle end, x,y,z (mm).
Point 7:		Left lower link axle end, x,y,z (mm).
Point 8:  	Left upper link axle end, x,y,z (mm).
Point 9:  	Watts cross link 1, x,y,z (mm).
Point 10:  	Watts cross link 2, x,y,z (mm).
Point 11:	Right spring/damper axle, x,y,z (mm).
Point 12:	Right spring/damper body, x,y,z (mm).
Point 13:	Left spring/damper axle, x,y,z (mm).
Point 14:	Left spring/damper body, x,y,z (mm).
Point 15:	Centre pivot point, x,y,z (mm).
Point 16:	Right wheel centre, x,y,z (mm).
Point 17:	Left wheel centre, x,y,z (mm).
Point 18:	Wheel stub axle point, x,y,z (mm).
Point 19:	Watts upper link axle end, x,y,z (mm).
Point 20:	Watts upper link body end, x,y,z (mm).
Point 21:	Watts lower link axle end, x,y,z (mm).
Point 22:	Watts lower link body end, x,y,z (mm).

Point 23:	Part 1 C of G
Point 24:	Part 2 C of G
Point 25:	Part 3 C of G
Point 26:	Part 4 C of G
Point 27:	Part 5 C of G
Point 28:	Part 6 C of G
Point 29:	Part 7 C of G
Point 30:	Part 8 C of G
Point 31:	Part 9 C of G

{bmc bm277.bmp}
Suspension Type 21, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 22: Double Wishbone, Twin Outer Ball Joints, Spring to Front Link

Type 22    Double wishbone, twin outer ball joints, spring to front link.

Point 1:  	Lower wishbone front inner pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear inner pivot, x,y,z (mm).
Point 3:  	Lower wishbone front outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front inner pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear inner pivot, x,y,z (mm).
Point 6:		Upper wishbone front outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Lower wishbone rear outer ball joint, x,y,z (mm).
Point 16:	Upper wishbone rear outer ball joint, x,y,z (mm).

Point 17:	Part 1 C of G
Point 18:	Part 2 C of G
Point 19:	Part 3 C of G
Point 20:	Part 4 C of G
Point 21:	Part 5 C of G
Point 22:	Part 6 C of G

{bmc bm278.bmp}
Suspension Type 22, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 23: Double Wishbone, Twin Outer Ball Joints, Anti-Roll Bar

Type 23    Double wishbone, twin outer ball joints, anti-roll bar.

Point 1:  	Lower wishbone front inner pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear inner pivot, x,y,z (mm).
Point 3:  	Lower wishbone front outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front inner pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear inner pivot, x,y,z (mm).
Point 6:		Upper wishbone front outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G

Point 19:	Lower wishbone front inner pivot(2), x,y,z (mm).
Point 20:	Lower wishbone rear inner pivot(2), x,y,z (mm).
Point 21:	Lower wishbone front outer ball joint(2), x,y,z (mm).
Point 22:	Upper wishbone front inner pivot(2), x,y,z (mm).
Point 23: 	Upper wishbone rear inner pivot(2), x,y,z (mm).
Point 24:	Upper wishbone front outer ball joint(2), x,y,z (mm).
Point 25:	Damper wishbone end(2), x,y,z (mm).
Point 26: 	Damper body end(2), x,y,z (mm).
Point 27:	Outer track rod ball joint(2), x,y,z (mm).
Point 28:	Inner track rod ball joint(2), x,y,z (mm).
Point 29:	Upper spring pivot point(2), x,y,z (mm).
Point 30:	Lower spring pivot point(2), x,y,z (mm).
Point 31:	Wheel spindle point(2), x,y,z (mm).
Point 32:	Wheel centre point(2), x,y,z (mm).

Point 33:	Part 1 C of G(2)
Point 34:	Part 2 C of G(2)
Point 35:	Part 3 C of G(2)
Point 36:	Part 4 C of G(2)

Point 37:	Roll Bar Attachment 1
Point 38:	Roll Bar Attachment 2
Point 39:	Roll Bar to Link 1
Point 40:	Roll Bar to Link 2
Point 41:	Roll Bar Mount 1
Point 42:	Roll Bar Mount 2
Point 43:	Roll Bar Revolute
Point 44:	Drop Link 1 C of G
Point 45:	Drop Link 2 C of G
Point 46:	Roll Bar 1 C of G
Point 47:	Roll Bar 2 C of G

{bmc bm279.bmp}
Suspension Type 23, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 24: Steerable Macpherson Strut, Twin Outer Ball Joints

Type 24    Steerable Macpherson strut, twin outer ball joints.

Point 1:  	Lower wishbone inner front pivot, x,y,z (mm).
Point 2:  	Lower wishbone inner rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer front ball joint, x,y,z (mm).
Point 4:  	Lower wishbone outer rear ball joint, x,y,z (mm).
Point 5: 	Strut slider upper axis point, x,y,z (mm).
Point 6:		Strut top point, x,y,z (mm).
Point 7:		Strut slider lower axis point, x,y,z (mm).
Point 8:		Outer track rod ball joint, x,y,z (mm).
Point 9:		Inner track rod ball joint, x,y,z (mm).
Point 10:	Upper spring pivot point, x,y,z (mm).
Point 11:	Lower spring pivot point, x,y,z (mm).
Point 12:	Wheel spindle point, x,y,z (mm).
Point 13:	Wheel centre point, x,y,z (mm).

Point 14:	Part 1 C of G
Point 15:	Part 2 C of G
Point 16:	Part 3 C of G
Point 17:	Part 4 C of G
Point 18:	Part 5 C of G

{bmc bm280.bmp}
Suspension Type 24, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 25: Double Wishbone, Twin Lower Outer Ball Joints

Type 25    Double wishbone, twin lower outer ball joints.

Point 1:  	Lower wishbone front inner pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear inner pivot, x,y,z (mm).
Point 3:  	Lower wishbone front outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front inner pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear inner pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).
Point 15:	Lower wishbone rear outer ball joint, x,y,z (mm).

Point 16:	Part 1 C of G
Point 17:	Part 2 C of G
Point 18:	Part 3 C of G
Point 19:	Part 4 C of G
Point 20:	Part 5 C of G

{bmc bm281.bmp}
Suspension Type 25, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 26: Double Wishbone, Damper to Lower Wishbone, Compliant Rack

Type 26    Double wishbone, damper to lower wishbone, compliant rack.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer ball joint, x,y,z (mm).
Point 4:  	Upper wishbone front pivot, x,y,z (mm).
Point 5: 	Upper wishbone rear pivot, x,y,z (mm).
Point 6:		Upper wishbone outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8: 	Damper body end, x,y,z (mm).
Point 9:		Outer track rod ball joint, x,y,z (mm).
Point 10:	Inner track rod ball joint, x,y,z (mm).
Point 11:	Upper spring pivot point, x,y,z (mm).
Point 12:	Lower spring pivot point, x,y,z (mm).
Point 13:	Wheel spindle point, x,y,z (mm).
Point 14:	Wheel centre point, x,y,z (mm).

Point 15:	Part 1 C of G
Point 16:	Part 2 C of G
Point 17:	Part 3 C of G
Point 18:	Part 4 C of G

Point 19:  	Lower wishbone front pivot(2), x,y,z (mm).
Point 20:  	Lower wishbone rear pivot(2), x,y,z (mm).
Point 21:  	Lower wishbone outer ball joint(2), x,y,z (mm).
Point 22:  	Upper wishbone front pivot(2), x,y,z (mm).
Point 23: 	Upper wishbone rear pivot(2), x,y,z (mm).
Point 24:	Upper wishbone outer ball joint(2), x,y,z (mm).
Point 25:	Damper wishbone end(2), x,y,z (mm).
Point 26: 	Damper body end(2), x,y,z (mm).
Point 27:	Outer track rod ball joint(2), x,y,z (mm).
Point 28:	Inner track rod ball joint(2), x,y,z (mm).
Point 29:	Upper spring pivot point(2), x,y,z (mm).
Point 30:	Lower spring pivot point(2), x,y,z (mm).
Point 31:	Wheel spindle point(2), x,y,z (mm).
Point 32:	Wheel centre point(2), x,y,z (mm).

Point 33:	Part 1 C of G(2)
Point 34:	Part 2 C of G(2)
Point 35:	Part 3 C of G(2)
Point 36:	Part 4 C of G(2)

Point 37:	Rack Link P1
Point 38:	Rack Link P2
Point 39:	Rack Mount P1
Point 40:	Rack Mount P2
Point 41:	Rack Link C of G
Point 42:	Rack Housing C of G

{bmc bm282.bmp}
Suspension Type 26, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 27: Steerable Macpherson Strut, Twin Lower Link

Type 27    Steerable Mac strut, twin lower link.

Point 1:  	Front lower link inboard, x,y,z (mm).
Point 2:  	Rear lower link inboard, x,y,z (mm).
Point 3:  	Front lower link outboard, x,y,z (mm).
Point 4:  	Rear lower link outboard, x,y,z (mm).
Point 5: 	Strut slider upper axis point, x,y,z (mm).
Point 6:		Strut top point, x,y,z (mm).
Point 7:		Strut slider lower axis point, x,y,z (mm).
Point 8:		Steering arm outboard end, x,y,z (mm).
Point 9:		Steering arm inboard end, x,y,z (mm).
Point 10:	Spring top centre line, x,y,z (mm).
Point 11:	Spring bottom at centre line, x,y,z (mm).
Point 12:	Wheel spindle point, x,y,z (mm).
Point 13:	Wheel centre point, x,y,z (mm).

Point 14:	Part 1 C of G
Point 15:	Part 2 C of G
Point 16:	Part 3 C of G
Point 17:	Part 4 C of G
Point 18:	Part 5 C of G

{bmc bm283.bmp}
Suspension Type 27, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 28: 4-Link Rear, Transverse Control Link

Type 28    4-Link Rear, Transverse Control Link.

Point 1:  	Lower wishbone front pivot, x,y,z (mm).
Point 2:  	Lower wishbone rear pivot, x,y,z (mm).
Point 3:  	Lower wishbone outer front pivot point, x,y,z (mm).
Point 4:  	Lower wishbone outer rear pivot point, x,y,z (mm).
Point 5:  	Upper front link inner ball joint, x,y,z (mm).
Point 6: 	Upper front link outer ball joint, x,y,z (mm).
Point 7:		Damper wishbone end, x,y,z (mm).
Point 8:		Damper body end, x,y,z (mm).
Point 9:		Upper spring pivot point, x,y,z (mm).
Point 10:	Lower spring pivot point, x,y,z (mm).
Point 11:	Wheel spindle point, x,y,z (mm).
Point 12:	Wheel centre point, x,y,z (mm).
Point 13:	Upper rear link inner ball joint, x,y,z (mm).
Point 14:	Upper rear link outer ball joint, x,y,z (mm).
Point 15:	Drop link to upright, x,y,z (mm).

Point 16:	Part 1 C of G
Point 17:	Part 2 C of G
Point 18:	Part 3 C of G
Point 19:	Part 4 C of G
Point 20:	Part 5 C of G

{bmc bm284.bmp}
Suspension Type 28, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 29: Twist Beam – Twin Wheel

Type 29    Twist Beam – Twin Wheel

Point 1:  	Trailing arm body point right, x,y,z (mm).
Point 2:  	Trailing arm body point left, x,y,z (mm).
Point 3:  	Shear point right, x,y,z (mm).
Point 4:  	Right damper lower trailing arm end, x,y,z (mm).
Point 5:  	Right damper body end, x,y,z (mm).
Point 6: 	Right upper spring pivot point, x,y,z (mm).
Point 7:		Right lower spring pivot point, x,y,z (mm).
Point 8:		Wheel spindle point 1, x,y,z (mm).
Point 9:		Wheel centre point 1, x,y,z (mm).
Point 10:	wheel centre point 2, x,y,z (mm).
Point 11:	Wheel spindle point 2, x,y,z (mm).
Point 12:	Left damper lower trailing arm end, x,y,z (mm).
Point 13:	Left damper body end, x,y,z (mm).
Point 14:	Left upper spring pivot point, x,y,z (mm).
Point 15:	Left lower spring pivot point, x,y,z (mm).
Point 16:	Shear point left, x,y,z (mm).
Point 17:	Twist beam point right, x,y,z (mm).
Point 18:	Twist beam point left, x,y,z (mm).
Point 19:	Centre connection point, x,y,z (mm).

Point 20:	Part 1 C of G
Point 21:	Part 2 C of G

{bmc bm285.bmp}
Suspension Type 29, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – Type 30: Generic 5-Link Rear

Type 30    Generic 5-Link Rear

Point 1:  	Link1 Inboard, x,y,z (mm).
Point 2:  	Link 1 Outboard, x,y,z (mm).
Point 3:  	Link 2 Inboard, x,y,z (mm).
Point 4:  	Link2 Outboard, x,y,z (mm).
Point 5:  	Link 3 Inboard, x,y,z (mm).
Point 6: 	Link 3 Outboard, x,y,z (mm).
Point 7:		Link 4 Inboard, x,y,z (mm).
Point 8:		Link 4 Outboard, x,y,z (mm).
Point 9:		Link 5 Inboard, x,y,z (mm).
Point 10:	Link 5 Outboard, x,y,z (mm).
Point 11:	Spring Damper to Body, x,y,z (mm).
Point 12:	Spring Damper to Upright, x,y,z (mm).
Point 13:	Stub Axle, x,y,z (mm).
Point 14:	Wheel Centre, x,y,z (mm).

Point 15:	Link 1 C of G
Point 16:	Link 2 C of G
Point 17:	Link 3 C of G
Point 18:	Link 4 C of G
Point 19:	Link 5 C of G
Point 20:	Upright C of G

{bmc bm286.bmp}
Suspension Type 30, LSA Screen Shot – Default Co-ordinates

+$#>Data Requirements – 3D Solver Tolerances

The 3D Solver uses a number of tolerances to control the calculation process.

Kinematic Solution Tol.,  (real),  (units none),  (default 1.e-10)
Controls the solution tolerance used by the kinematic solver in identifying the convergence limit.
The kinematic solver uses a hybrid approach to find a zero of a system of n non-linear functions in n variables by a modification of the Powell hybrid method.

Bump Small Perturbation Size,  (real),  (units mm),  (default 0.05 mm)
The standard approach used by the solver to determine certain derivatives at each suspension step position is to use a small incremental bump displacement. The size of this bump perturbation can be changed if necessary to improve solution stability.

Steer Small Perturbation Size,  (real),  (units mm),  (default 0.05 mm)
For steerable suspension templates that do not have a identified top and bottom ball joint, the standard approach used by the solver to determine the steering axis at each suspension step position is to use a small incremental steer displacement. The size of this steer perturbation can be changed if necessary to improve solution stability.

Toolbox Auto-Adjust angle Tolerance,  (real),  (units deg),  (default 0.005 mm)
Sets the tolerance used by the toolbox utility when adjusting a component length to achieve a desired static angle. The solver continues lengthening or shortening the selected component until the camber, castor or toe angle (as required) is within this tolerance from the desired static value.

Kinematic Solver Bump Seeding Size,  (real),  (units mm),  (default 0.05 mm)
This value is used as part of the solver seeding for unsolved points. At the start of each solution step initial values are supplied to all the unknowns to start the solution iteration, to avoid numerical issues of identical points the z position for moving points is seeded by a small amount of change from the previous solutions position. The size of this seeding value can be changed if necessary to improve solution stability.

{bmc bm287.bmp}
Solver Tolerances Display

+$#>Data Requirements – 3D General Defaults

Control of certain display features relies on a set of user controllable values.

Min Allowable Scale Factor,  (real),  (units none),  (default 0.00001)
Sets the minimum scale factor allowed when zooming or dynamically viewing the graphics display. This stops the viewing pipeline from failing through excessive zooming out.

Max Allowable Scale Factor,  (real),  (units none),  (default 500)
Sets the maximum scale factor allowed when zooming or dynamically viewing the graphics display. This stops the viewing pipeline from failing through excessive zooming in.

Tolerance on Point Pick,  (real),  (units none),  (default 0.05)
Defines the size of the pick circle used to check if a point has been selected with the mouse. The value is in 2d screen size, where ‘1’ is the full screen length. A larger number will make the selection easier but increase the chance of mis-selection.

Tolerance on Coincident Point Pick,  (real),  (units none),  (default 0.02)
Defined the screen size value used to determine whether two or more points are considered to be coincident. A greater value will lead to more instances of points being considered coincident. 

Joggle Step Size,  (real),  (units mm),  (default 10 mm)
Sets the step size used for joggle mode editing. This is the coarse step size, (Ctrl + arrow), whilst the fine step size, (Shift + arrow), will be 1/10th of this.

Animation Update,  (real),  (units mSec),  (default 50 mSec)
Defines the fastest rate for which animation will update. Machines unable to refresh at this rate will draw at their maximum speed, whilst high specification PC’s will be clipped to the defined refresh speed. Reducing this value will increase animation frame rate on high end PC’s.

Results Menu Switch,  (integer),  (units -),  (default 1)
Debug option used on previous version due to problems with the results menu being greyed out and not being able to status it back on as required. When set to 0 avoids statusing ‘off’ the results menu..

{bmc bm288.bmp}
General Defaults Display

+$#>Data Requirements – Deformed Geometry Scalar

The display of the compliant model displacements has a specific scalar display setting.

Deformed Geometry Scalar,  (real),  (units none),  (default 1.0)
To assist in viewing the model deflections due to the compliance effects a scalar value is editable. This is equivalent to the Finite-element modal analysis scalar value. Note that this controls both the static display and the animation when in ‘compliant’ mode.

{bmc bm289.bmp}
Setting the compliant graphics deformed geometry scalar

+$#>Data Requirements – Deformed Geometry Position

The animation display of the compliant model occurs at a defined incremental position.

Deformed Geometry Position,  (integer),  (units none),  (default 0)
The animation of compliant deformed geometry is drawn at a defined position. The default setting for this is to animate it at the static position, (0). The deformed geometry at alternative incremental steps can be performed by changing this value. This value is internally clipped to the maximum number of steps available.

{bmc bm290.bmp}
Setting the compliant graphics deformed geometry position

+$#>Data Requirements – Enhanced Graphic Sizes

The Enhanced graphics elements have a number of dimensional properties that can be defined by the user.

Spring Radius,  (real),  (units mm),  (default 45 mm)
The graphical radius of the suspension spring is drawn to this radius.

No of Spring Coils (max 60),  (integer),  (units mm),  (default 10)
Sets the No. of coils used when drawing the suspension spring.

Lower Damper Tube Radius,  (real),  (units mm),  (default 25 mm)
Sets the radius for the lower tube of the damper enhanced graphics element.

Upper Damper Tube Radius,  (real),  (units mm),  (default 30 mm)
Sets the radius for the upper tube of the damper enhanced graphics element.

Damper Number of Facets (max 19),  (integer),  (units mm),  (default 10)
The detail of the cylinder used to draw a damper element is controlled by a number of facets.

Pivot Radius,  (real),  (units mm),  (default 10 mm)
Defines the radius of the cylinder used to graphically illustrate model parts that have been identified as pivot axes.

Pivot No. of Facets (max 19),  (integer),  (units mm),  (default 8)
The detail of the cylinder used to draw a pivot is controlled by a number of facets.

Tyre No of Facets (max 31),  (integer),  (units mm),  (default 21)
The detail of the facetted tyre representation is controlled by this value.

Tyre Diameter Shoulder (0-1),  (real),  (units mm),  (default 0.9)
Sets the value for the diameter of the tyre shoulder as a fraction of the rolling radius. The shoulder is the tapered section of the graphical representation.

Tyre Width Shoulder (0-1),  (real),  (units mm),  (default 0.75 mm)
Sets the value for the width of the tyre excluding the shoulder as a fraction of the width. The shoulder is the tapered section of the graphical representation.

3D Tracking Line Length,  (real),  (units mm),  (default 150 mm)
Sets the length of the tracking line drawn through each hard point when in edit mode.

Joggle Symbol Size,  (real),  (units none),  (default 0.05)
Defines the size of the joggle symbol used to indicate the current point when in joggle mode. Size is based on screen size.

C of G Symbol Size,  (real),  (units mm),  (default 25 mm)
Defines the diameter of the symbol used to represent the position of the C of G symbol.

Grid Size,  (real),  (units mm),  (default 200 mm)
Sets the size of the squares used to draw the ground plane grid.

3D Line Clipping Length,  (real),  (units mm),  (default 2000 mm)
Sets the clipped size for graphical lines that have no defined length, such as cross product vectors.

3D Plane Clipping Length,  (real),  (units mm),  (default 1000 mm)
Sets the clipped size for graphical planes that have no defined size.

BumpStop Cone Upper Radius,  (real),  (units mm),  (default 60 mm)
Sets the radius used for the upper radius of the bump stop graphical cone.

BumpStop Cone Lower Radius,  (real),  (units mm),  (default 20 mm)
Sets the radius used for the lower radius of the bump stop graphical cone.

BumpStop Number of Facets (max 19),  (integer),  (units mm),  (default 10)
The detail of the cone used to draw a bumpstop element is controlled by a number of facets.

Virtual Steer Axis Length,  (real),  (units mm),  (default 2000 mm)
Sets the length of the virtual steer axis.

Local Coordinate Axis Length,  (real),  (units mm),  (default 60 mm)
Sets the length of the local coordinate axis systems drawn on the graphical display.

{bmc bm291.bmp}
Editing the Enhanced graphics sizes

+$#>Data Requirements – Graphics Label Sizes

The text labels drawn on the graphics display can be set by the user.

Point Value Size,  (real),  (units mm),  (default 20 mm)
Sets the size of the text used to identify the model template point Nos.

Point No. Size,  (real),  (units mm),  (default 20 mm)
Sets the size of the text used to identify the model hard point co-ordinates.

{bmc bm292.bmp}
Editing the Enhanced graphics label sizes

+$#>Data Requirements – Compliance Graphic Sizes

The Compliance graphics elements have a number of dimensional properties that can be defined by the user.

Ball Joint Radius,  (real),  (units mm),  (default 15 mm)
Defines the radius of the ‘Rigid’ ball joints in the compliant model.

Ball Joint Circumferential Complexity,  (integer),  (units none),  (default 10)
Sets the number of facets applied to the ball joint in the circumferential direction.

Ball Joint Height Complexity,  (integer),  (units none),  (default 10)
Sets the number of facets applied to the ball joint in the height direction.

Bush Radius,  (real),  (units mm),  (default 12 mm)
Defines the radius of the ‘Bush’ elements in the compliant model.

Bush Length,  (real),  (units mm),  (default 30 mm)
Defines the length of the ‘Bush’ elements in the compliant model.

Bush Circumferential Complexity,  (integer),  (units none),  (default 10)
Sets the number of facets applied to the bush in the circumferential direction.

Bush Height Complexity,  (integer),  (units none),  (default 4)
Sets the number of facets applied to the bush in the height direction.

Bush Axis Length,  (real),  (units mm),  (default 60 mm)
Defines the length of the lines used to indicate the bush local axes.

Tyre Spring Radius,  (real),  (units mm),  (default 12 mm)
Defines the radius of the springs for the compliant tyre element.

Force / Torque Fixed Head Size,  (real),  (units mm),  (default 30 mm)
Defines the size of the internal and external force and torque heads, when the display is set to fixed head size.

Force / Torque Fixed Length,  (real),  (units mm),  (default 300 mm)
Defines the length of any force or torque arrow, when display is set to fixed length.

Force Scaled Length,  (real),  (units mm/N),  (default 0.2 mm/N)
Defines the scale factor applied to forces when force display is set to variable length and/or variable head.

Torque Scaled Length,  (real),  (units mm/N.mm),  (default 0.002 mm/N.mm)
Defines the scale factor applied to torque’s when torque display is set to variable length and/or variable head.

Force Value Size,  (real),  (units mm),  (default 6.00 mm)
Defines the screen size of the force value label.

{bmc bm293.bmp}
Editing the Compliance graphics sizes

+$#>Data Requirements – Graph Markers and Text Sizes

The user can define the graph marker sizes. Additionally the text sizes on the graphs and the compliance results can be set by the user.

Data Marker Size,  (real),  (units screen size 0-1),  (default 0.05)
Defines the size of the marker symbols for the graph Data lines

Scope Marker Size,  (real),  (units screen size 0-1),  (default 0.05)
Defines the size of the marker symbols for the graph Scope lines

User Marker Size,  (real),  (units screen size 0-1),  (default 0.05)
Defines the size of the marker symbols for the graph User lines

Graph Data Values Text Size,  (real),  (units screen size 0-1),  (default 0.03)
Defines the size of the text used to display values of points on the graphs.

Compliance Title Text Size,  (real),  (units screen size 0-1),  (default 0.1)
Defines the size of the text used to display the graph titles on the compliance coefficient results display.

Compliance Label Text Size,  (real),  (units screen size 0-1),  (default 0.067)
Defines the size of the text used to display the variables labels on the compliance coefficient results display.

Compliance Values Text Size,  (real),  (units screen size 0-1),  (default 0.067)
Defines the size of the text used to display the compliance coefficients on the bar chart results display.

{bmc bm294.bmp}
Editing the Graph marker and text sizes

+$#>Data Requirements – Graphs Decimal Points Display

The user can define the number of decimal points used on the graph display for individual value displays.

X-Data Listing,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the X data value list.

Y-Data Listing,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the Y data value list.

Derivative Data Listing,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the derivative value on the data list.

Scope Deviation,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the display of the deviation between the data and scope lines.

User Deviation,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the display of the deviation between the data and user lines.

X-Axis Label,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the displayed X-Axis value labels.

Y-Axis Label,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the displayed Y-Axis value labels.

Compliance Graph Values,  (integer),  (units none),  (default 3)
Sets the number of decimal points for the displayed bar chart values on the compliance graphs.

{bmc bm295.bmp}
Editing the displayed Graph Decimal Points settings

+$#>Data Requirements – 3D Point Tolerances

Individual point tolerances can be edited by locating the point and tolerance of interest through the tree structure presented and setting the actual limiting value. All point tolerances can be set in one go by defining the ‘delta’ from their current position in each axis and direction.

For the individual point tolerances setting, select from tree structure and then edit from;

{bmc bm296.bmp}
Selecting the Point and tolerance to Edit from the tree display

Min X,  (real),  (units mm),  (default none)
Sets the minimum allowed hard point value in the X-axis direction.

Max X,  (real),  (units mm),  (default none)
Sets the maximum allowed hard point value in the X-axis direction.

Min Y,  (real),  (units mm),  (default none)
Sets the minimum allowed hard point value in the Y-axis direction.

Max Y,  (real),  (units mm),  (default none)
Sets the maximum allowed hard point value in the Y-axis direction.

Min Z,  (real),  (units mm),  (default none)
Sets the minimum allowed hard point value in the Z-axis direction.

Max Z,  (real),  (units mm),  (default none)
Sets the maximum allowed hard point value in the Z-axis direction.

{bmc bm297.bmp}
Individual Point Tolerance Editing

For the ‘all points’ tolerances setting, all tolerances are edited as positive difference values along each axis direction, (i.e. both positive and negative axis directions are entered as positive values;

-ve X Tolerance,  (real),  (units mm),  (default 25 mm)
Sets the tolerance in the –ve X-axis direction for the hard point value.

+ve X Tolerance,  (real),  (units mm),  (default 25 mm)
Sets the tolerance in the +ve X-axis direction for the hard point value.

-ve Y Tolerance,  (real),  (units mm),  (default 25 mm)
Sets the tolerance in the –ve Y-axis direction for the hard point value.

+ve Y Tolerance,  (real),  (units mm),  (default 25 mm)
Sets the tolerance in the +ve Y-axis direction for the hard point value.

-ve Z Tolerance,  (real),  (units mm),  (default 25 mm)
Sets the tolerance in the –ve Z-axis direction for the hard point value.

+ve Z Tolerance,  (real),  (units mm),  (default 25 mm)
Sets the tolerance in the +ve Z-axis direction for the hard point value.

{bmc bm298.bmp}
Editing ‘All’ point Tolerances

+$#>Data Requirements – 3D Spring Data

The suspension spring properties are used to define the spring forces applied to the compliant model, (when enabled). Incremental spring force properties are set by the combination of rate, free length, fitted length and the current spring displacement. Note that only linear rate springs can currently be modeled. All the properties are repeated twice (1) and (2) to support either corner models with two springs or full axle templates.

To edit the spring properties select Data / Compliance Data / Spring Properties…

Front Spring Rate,  (real),  (units N/mm),  (default 41.5 N/mm)
Sets the linear spring rate for the front suspension spring.

Rear Spring Rate,  (real),  (units N/mm),  (default 41.5 N/mm)
Sets the linear spring rate for the rear suspension spring.

Front Spring Free Length,  (real),  (units mm),  (default 300 mm)
Sets the free (un-compresed) length for the front suspension spring.

Rear Spring Free Length,  (real),  (units mm),  (default 300 mm)
Sets the free (un-compresed) length for the rear suspension spring.

Front Spring Fitted Length,  (real),  (units mm),  (default 246.5 mm)
Sets the fitted (installed) length for the front suspension spring.

Rear Spring Fitted Length,  (real),  (units mm),  (default 246.5 mm)
Sets the fitted (installed) length for the rear suspension spring.

{bmc bm299.bmp}
Editing the 3D Spring Data

+$#>Data Requirements – 3D Damper Data

The suspension damper properties are used to define the damping characteristics applied to the compliant model, (when enabled) via the main dampers. The damping due to bushes is included separately via a Bush Loss Angle number that can be edited via the Data / Compliance Data / General Data… menu option. Note that only linear damping can currently be modeled.

To edit the damper properties select Data / Compliance Data / Damper Properties…

Front Damper 1 Rate,  (real),  (units N/mm),  (default 0.4 N.s/mm)
Sets the damper rate for the front suspension damper 1 element.

Rear Damper 1 Rate,  (real),  (units N/mm),  (default 0.4 N.s/mm)
Sets the damper rate for the rear suspension damper 1 element.

Front Damper 2 Rate,  (real),  (units N/mm),  (default 0.4 N.s/mm)
Sets the damper rate for the front suspension damper 2 element.

Rear Damper 2 Rate,  (real),  (units N/mm),  (default 0.4 N.s/mm)
Sets the damper rate for the rear suspension damper 2 element.

{bmc bm300.bmp}
Editing the 3D Damper Data

+$#>Data Requirements – 3D Roll Bar Properties

The suspension roll bar properties are used to define the roll stiffness of the roll bar revolute joint, when included in a template. It only affects compliance results.

To edit the roll bar properties select Data / Compliance Data / Roll Bar Properties…

Front Roll Bar Rate,  (real),  (units N.mm/deg),  (default 2.0E6 N.mm/deg)
Sets the roll bar rate for the front suspension roll bar element.

Rear Roll Bar Rate,  (real),  (units N.mm/deg),  (default 2.0E6 N.mm/deg)
Sets the roll bar rate for the rear suspension roll bar element.

{bmc bm301.bmp}
Editing the 3D Roll Bar Properties

+$#>Data Requirements – 3D General Compliance Data

The compliant solver uses a number of standard constants in solving the compliant suspension model. These constants can be modified by the user through the data section.

To edit th ese general compliance properties select Data / Compliance Data / General Data…

Singularity Stiffness,  (real),  (units N/mm),  (default 10. N/mm)
Defines the stiffness value used within the solver to remove the singularity caused by components such as tie rods. Eliminates the degree of freedom using this arbitrary stiffness value.

Rigid (Ball Joint) Stiffness,  (real),  (units N/mm),  (default 1.0e8 N/mm)
For ball joints defined as ‘rigid’ the compliant solver will treat as high stiffness bushes with a constant 3x translational stiffness and 3x zero rotational stiffness. This is the value used for the high translational stiffness.

Rigid Rotation Stiffness,  (real),  (units N.mm/deg),  (default 1.0e8 N.mm/deg)
For joints defined as ‘rotational’ the compliant solver will treat as a a 6 d.o.f. bush with a constant 3x high translational stiffness and 2x high rotational stiffness. This is the value used for the high rotational stiffness. The translational stiffness is taken as the value above.

Bush Loss Angle,  (real),  (units deg),  (default 3.0 deg)
Defines the default damping value for a bush. User defined values for individual bushes will overwrite this setting.

Default Compliant Stiffness,  (real),  (units N/mm),  (default 1.0e3 N/mm)
For bushes this is used to fill the default 3 translational stiffness values when switched from a ‘rigid’ ball joint to a compliant bush.

Default Rotation Stiffness,  (real),  (units N.mm/deg),  (default 1.0e6 N/mm)
For certain bushes this is used to fill the default 3 rotational stiffness values when used as a bush that requires some rotational stiffness other than ‘rigid’.

{bmc bm302.bmp}
Editing the 3D General Compliance Data

+$#>Data Requirements – 3D User Definable Templates

Template Properties

Each of the template types hard coded into Shark uses a series of properties to identify its form. The properties include;

	Template Number
	Template Label
	No of Parts
	Part Labels
	No of Points
	Point Labels/Point Number
	Point default x, y and z values
	No of Bushes
	Point attachments to parts
	Point Types
	No of Graphical Elements
	Graphical element type
	Graphical element associated points

Together with some additional properties this allows the application to both build, display and analyze the kinematic and compliant models for each template.

Hard Coded Templates

By default some 30 templates are hard coded into the application. These are the ones listed in this help file under the 3D suspension templates section. It is important to notice that these hard coded templates have a template index number. This allows the data files to refer to a template type by its index number when loaded, using the model structure as defined by the internal template, just replacing the default x, y and z co-ordinates with those in the model file.

Adding to the Templates

It is possible to add to, (or indeed replace), the standard hard coded templates in two ways. The first is termed as ‘default’ templates, which are automatically loaded on program start-up. Whilst the second is termed ‘user’ templates and need to be loaded directly by the user once the application is open. Both ‘default’ and ‘user’ templates are stored in ASCII text files that could be edited/viewed through any standard text editor.

Default Templates

The ‘default’ templates are loaded on program start-up from the file ‘_User_Templates.Dat’. This file is searched for in the applications start-up folder, (normally C:\lesoft), and if found is read in. As with the ‘hard coded’ templates each entry in the default templates file has a template index number, and the default templates properties will be stored at this location. Thus if the index number used clashes with one used by the hard coded templates the hard coded template data will be over written. Whilst this would normally not be recommended it may for example be useful just to change the default point co-ordinates for the hard coded template.

Restoring the Default Templates

The default templates would normally only be loaded on program start-up. It is possible to change the default templates through some external text editor such that you want to re-apply the default templates during a program run. This may also be required is a user defined template has inadvertently over-written a default template index and you require to re-read the default templates. To do this without having to quit the application select File / Re-Read Default Templates.

Loading User Defined Custom Templates

User defined templates are stored in ASCII text files having exactly the same file format as the ‘defaults’ file. As with the hard coded and default templates each entry in a file will have a template index number. This will be the template slot that will be filled with the following template properties. So as with user templates it is possible to over-write a hard coded or default template when reading in user template data. To load user defined templates from an existing file select File / Add Custom Templates and locate the required file via the browser.

Creating and Editing Templates

The easiest way of modifying and creating templates is to use the supplied template editing tool. This spread sheet based display allows you to view/modify existing templates or create new ones. To open the template editor select File / Edit Templates…

{bmc bm303.bmp}
Editing the 3D Template Properties – Parts Panel

The display is divided into 4 separate panels, For Parts, Points, Settings and Graphics. As the labels suggest. 

The Parts panel identifies how many parts their are in the template and gives each one a label. An additional part is assumed without it needing to be defined, that is the ground/body.

The Points panel defines how many points there are in the template, gives each one a label and a set of default co-ordinates.

The Settings panel defines how the model is connected. This is done by identifying which parts a point is attached too. If it is attached to two parts (including ground), this implies a connection between these two parts at the defined point. If a point is only attached to one point then it does not define a joint. Additionally the settings panel identify points that have a special function, (listed as gen type). Examples of these special functions damper attachment points, steering rack attachment etc. A point may have more than one special function, (listed under gen. type 1 and gen. type 2).

The graphics panel defines any additional graphical elements that the user requires to visualize the suspension template. A number of different graphic element types are available. By default graphical elements are automatically added for the wheel, stub axle, spring and damper and thus do not need to be added by the user.

Data types, Compulsory, Level 1, Level 2 and Level 3

Template properties are arranged in sets that are identified by colour.

Compulsory properties, (pale pink), are those that must be defined by the user these include all part and point panel properties together with 4 columns of the settings panel.

The other property sets are arranged into three levels, all of which can be filled automatically, but with decreasing levels of confidence. The automatic fill can be enabled and set to the required level via the Data / Auto Fill menu options. By default the Auto fill option is set to ‘off’.

Level 1, (pale mauve), involves identifying and numbering each of the bushes in the template. Setting the auto fill to level 1 or higher fill automatically populate the relevant column and value entry. This auto fill level is the most reliable and can be used with confidence.

Level 2, (pale green), involves identifying the solution type to be used with each point, column 2 of the settings panel. The combination of general type settings and part connections is used to identify the most suitable solution type from the 10 alternatives. Whilst this level of auto fill works for all the hard coded template types it may need some user intervention for new types, but should be used as a first fill.

Level 3, (pale yellow), covers the specific settings for each points solution, columns 6 to 11 for the settings panel. Where relevant it identifies which other points are used in each points solution. Some solution types require no points whilst some will require as many as six, (see the later discussion on this). This auto-fill level is the most likely to need user intervention to set the required properties.

Testing the Template

The settings panel properties are used by the solver to identify the number of unknowns, (i.e. solving for one hard point introduces three unknowns x, y and z), and the equations to use for solving these unknowns. Thus for a successful template settings it is required to have as many equations as unknowns. A utility is provide to pre-test the template properties to check for satisfying this criteria. To test the currently displayed template settings select the menu item Data / Run Validation Test. A scrollable text display is listed identifying the current unknowns versus equations status and the form of each equation. (See later section for discussion on solution types).

{bmc bm304.bmp}
Testing the 3D Template Settings

Settings Panel – General Types

One of the compulsory properties for each point is the General type setting. As stated previously a point may have more than one general type settings. General types are listed in columns 12 and 13. Not all of the general types need appear in every template, although some general types must appear in each. These ‘required’ general types are identified below.

 The fifteen general types are;

0 – None: Defines the point status as having no general type. Examples of this would be most suspension link attachment points to the body and track rod outer ball joints.

1 – Wheel Centre: Simple general type that tags the model point used for the wheel centre. Together with the general type 2 below identify the wheel spindle axis. (Required).

2 – Stub Axle: Simple general type that tags the model point used to identify the wheel spindle axis. See also type 1 above. (Required).

3 – Steering Attachment Point: Identifies which suspension link end point should be used for the steering input from the rack or steering box. The omission of a type 3 point indicates a non-steerable suspension template, and thus will only appear in the rear suspension templates list. This point should be the inboard end of the track rod, i.e. link point connected to body. (Optional).

4 – Damper 1 to Suspension: Identifies this point as being the attachment of the damper to the suspension system it also identifies the slider of a Macpherson strut. If this general type is not identified no damper travel and damper ratios will be determined. Examples of this general type include the lower point of a conventional damper and the point used to identify the slider of a Macpherson strut. (Optional except for strut suspensions).

5 – Damper 1 to Body (also Strut top): Identifies this point as being the upper attachment point of the damper to the body it also identifies the top of a Macpherson strut . If this general type is not identified no damper travel and damper ratios will be determined. Examples of this general type include the upper point of a conventional damper and the point used to identify the top mount of the Macpherson strut. (Optional except for strut suspensions).

6 – Spring 1 to Suspension: Identifies the attachment point of the spring to the suspension. In the case of a conventional coil-over spring damper this point may be the same as type 4 above. If omitted the spring travel and spring ratio parameters will not be calculated. This point would not normally be at a connection between two parts point. (Optional).

7 – Spring 1 to Body: Identifies the attachment point of the spring to the body. In the case of a conventional coil-over spring damper this point may be the same as type 5 above. If omitted the spring travel and spring ratio parameters will not be calculated. (Optional).

8 – Upper Ball joint: Identifies a point as being the upper ball joint for the steering axis. This must be a connection between two parts to conform with the concept of a steering axis. It is an optional setting in that if it (and the lower ball joint) are not defined the steering axis is determined via a small perturbation of the steering input mechanism. If it can be defined it will lead to faster solution times than the small perturbation method. (Optional).

9 – Lower Ball Joint: Identifies a point as being the lower ball joint for the steering axis. This must be a connection between two parts to conform with the concept of a steering axis. It is an optional setting in that if it (and the upper ball joint) are not defined the steering axis is determined via a small perturbation of the steering input mechanism. If it can be defined it will lead to faster solution times than the small perturbation method. (Optional).

10 – Strut Slider Point: Sets the point for a Macpherson strut suspension type that is considered to be the location of the top bush for the strut, (attached to the strut body). (Required for Struts).

11 – Strut Lower end Point: Sets the point for a Macpherson strut suspension type that is considered to be the location of the strut lower bush, (attached to the strut slider). (Required for Struts).

14 – Roll Bar, Link Attachment: Identifies the point as being the first connection between the roll bar drop link and the suspension. (Optional). Roll bars can only be added to full axle templates so a template must have both this and point 32 defined.

15 – Rack Lateral Mount Point: Identifies the point as being the connection between the rack and the body at which the lateral load is taken. Only required if compliant rack force is required on asymmetric loading. (Optional). 

16 – Rack Mount Point: Identifies the point as being the connection between the second rack connection point to the body. (Optional). 

17 – Wheel Centre (2): Identifies the point as being a second wheel centre. Typically this implies a rigid axle type of suspension template as it is normal to model independent suspension as individual corners. (Optional). 

18 – Damper 2 to Suspension: Identifies the point as being the connection between the second damper and the suspension. It could be the left hand side damper in a rigid axle template or the second damper in a two damper corner model, (Optional). 

19 – Damper 2 to Body: Identifies the point as being the connection between the second damper and the suspension. (Optional). 

20 – Spring 2 to Suspension: Identifies the point as being the connection between the second spring and the suspension. It could be the left hand side spring in a rigid axle template or the second spring in a twin spring corner model, (Optional). 

21 – Spring 2 to Body: Identifies the point as being the connection between the second spring and the suspension. (Optional). 

22 – Rigid Axle Revolute: Defines the point as being the revolute joint required by the over constrained rigid axle templates in kinematic mode. It adds a rotational degree of freedom to allow roll motion to occur kinematically. This rotation is then removed by applying equal and opposite torque’s in compliant mode as pre-loads of a stiff bush. (Optional). 

23 – Stub Axle (2): Identifies a second stub axle point used in twist beam type templates where both sides are modelled in one go but have different stub axle references.. (Optional). 

24 – Shear Point: Used just for twist beam suspensions to identify the different pivot point position used in bump and roll. (Optional).

25 – Part C of G Point: Used to identify a point as being the C of G point for its primary part. It is normal for this point to not be used except as the C of G point, i.e. no involved in any joints. (Optional).

26 – Upper Ball joint(2): Identifies a point as being the upper ball joint for the steering axis on full axle templates only. This must be a connection between two parts to conform with the concept of a steering axis. It is an optional setting in that if it (and the lower ball joint) are not defined the steering axis is determined via a small perturbation of the steering input mechanism. If it can be defined it will lead to faster solution times than the small perturbation method. (Optional).

27 – Lower Ball Joint(2): Identifies a point as being the lower ball joint for the steering axis on full axle templates only. This must be a connection between two parts to conform with the concept of a steering axis. It is an optional setting in that if it (and the upper ball joint) are not defined the steering axis is determined via a small perturbation of the steering input mechanism. If it can be defined it will lead to faster solution times than the small perturbation method. (Optional).

28 – Strut Slider Point(2) Sets the point for a Macpherson strut suspension type that is considered to be the location of the top bush for the strut for full axle templates only, (attached to the strut body). (Required for Struts).

29 – Strut Lower end Point(2): Sets the point for a Macpherson strut suspension type that is considered to be the location of the strut lower bush for full axle templates only, (attached to the strut slider). (Required for Struts).

32 – Roll Bar, Link Attachment(2): Identifies the point as being the second connection between the roll bar drop link and the suspension. (Optional). Roll bars can only be added to full axle templates so a template must have both this and point 14 defined.

33 – Steering Attachment Point(2): Identifies which suspension link end point should be used for the steering input from the rack or steering box for the second end in a full axle model only. See also point 3 above. This point should be the inboard end of the track rod, i.e. link point connected to body or rack. (Optional). For a compliant rack to be added to the model this point must be defined together with point 3 above.
In kinematic mode this is treated as a simple revolute allowing roll motion. In compliant mode the roll bar stiffness is applied to this point to simulate the effect of the roll bar stiffness. (Optional). Roll bars can only be added to full axle templates so a template must have this point and points 14 and 32 defined.

34 – Roll Bar Revolute Joint: Identifies the points the position used to represent the anti-roll bar stiffness. The bush associated with this point has its translational stiffness’ set to rigid and the local z-axis rotational stiffness set to the defined roll bar stiffness.

35 – Wheel Hub Compliance: Identifies the point as the wheel hub. In compliance mode the bush associated with this point, that connects the hub to the upright, is given the compliant hub stiffness properties.

36 – Wheel Hub Compliance(2): Identifies the point as the second wheel hub in a full axle template. In compliance mode the bush associated with this point, that connects the hub to the upright, is given the compliant hub stiffness properties.

37 – Outer CV Centre: Marks the point as being the centre of the outer CV joint. This would normally for automatically generated drive shafts also be the stub axle point.

38 – Outer CV Centre(2): Marks the point as being the centre of the second outer CV joint in a full axle template. This would normally for automatically generated drive shafts also be the stub axle(2) point.

39 – Inner CV Centre: Marks the point as being the centre of the inner CV joint. This point is used along with point 41 to apply drive shaft torque’s.

40 – Inner CV Centre(2): Marks the point as being the centre of the second inner CV joint in a full axle template. This point is used along with point 42 to apply drive shaft torque’s.

41 – Inner CV Axis: This point type, together with point type 39, (see above) define the axis of the inner CV joint. This axis is used to apply drive shaft torque’s.

42 – Inner CV Axis(2): This point type, together with point type 40, (see above) define the axis of the second inner CV joint for a full axle template. This axis is used to apply drive shaft torque’s.

43 – Spacer Point: This point type marks it as being associated with a connection between a spacer and a part. This tag enables spacer specific calculations to be performed.

44 – Spacer Vector Point: This point type marks it as being the axis point of a spacer. Spacer vectors control the orientation of the spacer offset and thus require this individual flag to enable spacer vector specific calculations to be performed.

{bmc bm305.bmp}
Template Settings – Type 1 General types

Settings Panel – Point Types

Point types can be auto filled with a reasonable level of confidence with auto fill set to level 2. The possible nine types are described below to enable direct user editing of this template setting. The equivalent required data values for columns 6 to 11 are also described.

0 – To Body/Ground: No unknowns or equation added to the main solver for this point type. No column 6 to 11 data required. Solver will pre calculate the positions of these points based on either incremental body bump or roll displacement. Example points would be any suspension attachment to body points.

1 – Solve Direct (Sphere): Adds three unknowns to the solver. Uses the spherical distance relationship of this point to any others listed in columns 6 to 11. Examples of this would be the outer ball joint of a conventional wishbone. Columns 6, 7 and 8 refer to other relevant points on part 1, whilst columns 9, 10 and 11 refer to other relevant points on part 2. As an example a lower wishbone outer ball joint would have two spherical equations with its two inboard body attachment points on its first part, and two spherical  equations with the upper wishbones outer ball joint and the track rod outer ball joint on its second part.

2 - Solve Post (Vector Pos): Does not add any unknowns or equations to the main solver for this point type. It is solved after the main solver calculation is complete and uses three other points on the same body to identify its new position. This would normally be used for points such as a springs’ attachment to a wishbone. The two pivot points and the outer ball joint define its position. Values need to be defined in columns 6, 7,and 8. No values would be expected in columns 9, 10 and 11.

3 – Define Z-pos (Wheel Centre): This type is only applicable to the wheel centre point. Solution for the wheel centre is based on a defined z position of the tyre contact point. The two unknowns of x and y are added to the solution. Requires three points to be defined in columns 6, 7 and 8 that identify three other points on part 1, (excluding the stub axle point).

4 – Solve Direct (Slider Conn): Specific point type for strut sliders. Equation based on retaining the relationship between the three strut axis points. Requires the strut top and strut lower point to be defined in columns 6 and 7 for the first part. Requires two points to be defined in columns 9 and 10 for points on part 2.

5 – Solve Post (Stub Axle): Specific point type for stub axle point. Solve method is based on a post main solver calculation that uses three other points on part 1 to define its position. Normally the wheel centre is given as one of the three.

6 – Solve direct (Slider Bottom): Specific type for the strut slider lower axis point. Requires the strut top point to be defined in column 6 for part 1.

7 – Solve via Hookes Joint: Normally only required if a simple spherical solution can’t be used because a force or connection is applied to a simple link element (i.e. two main suspension connections). An example of this is the mounting of a spring or anti-roll bar to a simple tie rod. The two main connection points are required in columns 6 and 7 for part 1.

8 – Solve Post (Sphere): A post main solver spherical calculation. Requires three defining points to be given in columns 6, 7 and 8 for part 1. Example is solution of roll bar drop link to roll bar position. Can only be applied to points that have no control over kinematic wheel position.

9 – Pre-Solve (Kine Fix): A pre main solver option calculation. Requires no defining points since the point is assumed to be inactive in kinematic mode. It remains fixed to the part it is defined on (normally ground or a ground fixed part). It is used to add additional compliance effects for parts such as rack mounts and sub frames that are assumed to have no kinematic effect but are included in the compliance matrix.

{bmc bm306.bmp}
Template Settings – Selecting Point Type

Solution Types

The solution types used by the main solver are based on one of six types. The particular type used for each depends on the point type settings discussed above.

A brief description of each solution type is given here:

1 – Sphere Equation: Spherical distance between point 1 and point 2.

2 – Distance to Vector: Perpendicular distance of point 1 from a vector drawn from point 2 to point 3.

3 – x-x Based Slope: The slope between point 1 and point 2 is constant in x-x, i.e. point 1 and two are on the same vector.

4 – y-y Based Slope: The slope between point 1 and point 2 is constant in y-y, i.e. point 1 and two are on the same vector.

5 – z-z Based Slope: The slope between point 1 and point 2 is constant in z-z, i.e. point 1 and two are on the same vector.

6 – Minimum Z value: The lowest point of solid disc at point 1 normal to an axis to point 2 has a lowest z value as defined.

Creating a New Template

The sequence of data entry for creating a new template should be:

1) Identify an empty index No.
2) On the ’Parts’ panel enter the template label.
3) On the ‘Parts’ panel define the number of parts, (make upright last part).
4) On the ‘Parts’ panel enter the part labels. Ensure the upright is the last part in the list.
5) Change to the ‘Points’ panel and define the number of points.
6) On the ‘Points’ panel define the point labels.
7) On the ‘Points’ panel enter the default x, y and z coordinates.
8) Change to the ‘Settings’ panel and set the Part 1 and Part 2 properties for each point.
9) On the ‘Settings’ panel define the relevant Gen. Type 1and Gen. Type 2 settings.
10) Set the Auto fit level to 3 and review the filled values.
11) Check the validity of the auto-filled values using the Data / Run Validation Test… option.
12) If necessary make modifications to columns 6 to 11 to pass test.
13) Change to ‘Graphics’ panel and add define number of graphical elements.
14) On the ‘Graphics’ panel enter graphical element data.

+$#>Data Requirements – Control Elements and Actuators

Control Element properties are used either to modify the position of a hard point (position actuator) or change length of a point to point distance (length actuator). This is a kinematic effect in that it will modify the kinematic motion as a function of the transducer input. The transducer can be the change in the length between two points, such as the damper upper and lower points. The transducer input can also be the Z-displacement of the ground/body (or of a identified point), finally it can also be the current roll angular displacement. The relationship between the transducer value and the change in length of the controller distance is defined by a point-by-point spline employing linear interpolation/extrapolation. Individual control elements can be applied to points/lengths in pairs to provide control for example in the case of a pivot axis where you wish to move both axis-defining points.

To edit the control element properties pick the relevant control elements ‘hot spot’ in the graphical display. (if they are not visible turn on visibility via Graphics / Enhanced visibility / Actuator).

For the “Position Actuator” the properties are…

{bmc bm307.bmp}
Editing the “Position Actuator” Control Element Properties

Label,  (string),  (units -),  (Added via Pick)
Identifies an individual label for the actuator.

Static Colour,  (choice),  (units -),  (default ‘Cyan’)
Sets the colour used to draw all actuators at the static position.

Incremental Colour,  (choice),  (units -),  (default ‘Blue’)
Sets the colour used to draw all actuators at any position other than ‘static’.

Tube 1 Diameter,  (real),  (units mm),  (default 5.0 mm)
Sets the graphical size of tube 1 for all actuators.

Tube 2 Diameter,  (real),  (units mm),  (default 10.0 mm)
Sets the graphical size of tube 2 for all actuators.

No. of Facets,  (integer),  (units -),  (default 10 )
Sets the number of radial facets used to draw the actuator cylinders for all actuators.

Fixed Length,  (real),  (units mm),  (default 150 mm)
Defines the length of the fixed portion of all the ‘position’ actuator.

Edit Control Data Spline,  (real),  (units mm or deg as appropriate),  (default spline)
Defines the relationship between the transducer measured property and the applied actuator change. In its simplest form this could be the ratio for the change in lengths.

{bmc bm308.bmp}
Editing the “Control Spline” for a Control Element

Actuator 1 Pnt1,  (choice),  (units -),  (default picked point)
Identifies the point whose position will be modified by the position actuator, (normally selected from the graphical display with the mouse as part of the creation process).

Vector (dx/dy/dz),  (real),  (units -),  (default 0.0/1.0/0.0)
Sets the actuator vector used for the point displacement, i.e. the points position will be moved along this vector by the actuator.

Transducer Pnt1,  (choice),  (units -),  (default damper lower)
Sets the first point of the transducer. Can be a hard point (for the change in position between two points) or the Z-displacement of the ground, body or the point specified in “Transducer Pnt2”.

Transducer Pnt2,  (choice),  (units -),  (default damper upper)
Sets the second point of the transducer. Can be a hard point (for the change in position between two points) or the point referenced by a Z-displacement selection in “Transducer Pnt1”.

Actuator 2  Scaler,  (real),  (units -),  (default 1.0)
Sets the displacement scale used between the “Actuator Pnt1” and the optional “Actuator Pnt2”. Actuator Pnt2 will use the same displacement vector as Pnt1 but its displacement will be the Scaler times the displacement of Actuator Pnt1.

Enhanced Visibility,  (On/Off switch),  (units -),  (default On)
Control the visibility in the graphics display of all control elements.

For the “Length Actuator” the properties are the same as for the above position actuator with the exception of…

{bmc bm309.bmp}
Editing the “Length Actuator” Control Element Properties

Actuator 1 Pnt1,  (choice),  (units -),  (default picked point)
Identifies the first point involved in the controlled length of the length actuator, (normally selected from the graphical display with the mouse as part of the creation process).

Actuator 1 Pnt2,  (choice),  (units -),  (default picked point)
Identifies the second point involved in the controlled length of the length actuator, (normally selected from the graphical display with the mouse as part of the creation process).

Actuator 2 Pnt1,  (choice),  (units -),  (default none)
For the optional second control length, identifies the first point involved in the controlled length of the length actuator. Select from available list.

Actuator 2 Pnt2,  (choice),  (units -),  (default none)
For the optional second control length, identifies the second point involved in the controlled length of the length actuator. Select from available list.

+$#>Data Requirements – Body Centre of Gravity Properties

To edit the body C of G properties pick the C of G symbol through the graphical interface, (if it is not visible turn on visibility via Graphics / Enhanced visibility / Body C of G Marker). These properties can also be edited via the pull down menu Data / Parameters… Although the label may be misleading with the use of the word ‘body’, it is in reality the total overall vehicle C of G property and not just the ‘body’.

{bmc bm310.bmp}
Editing the Body C of G Properties

For the “Body Centre of Gravity” the properties are…

Graphic Size,  (real),  (units mm),  (default 25 mm)
Sets the size of the on screen graphic used to identify and locate the ‘hot spot’ for the body G of G point.

C of G Height,  (real),  (units mm),  (default 250 mm)
Defines the height above the ground plane of the vehicle C of G, (note this is not the global Z position but Z height relative to the ground plane).

Total Weight Front,  (real),  (units %),  (default 40 %)
Sets the percentage of the total vehicle weight associated with front, (i.e. together with the wheelbase this positions the axial position of the vehicle C of G.

Total Sprung Weight,  (real),  (units kg),  (default 0.0 kg)
Defines the amount of the total vehicle mass that is considered to be ‘sprung’. This value is only used as part of the “Ride Height” options, where it is also prompted for.

Enhanced Visibility,  (On/Off switch),  (units -),  (default On)
Control the visibility in the graphics display of the C of G symbol.

+$#Data Requirements – Graphical Element Properties

A large number of different graphical element types are available within LSA from simple lines joining two points through cylinders, spheres, planes and facets. Each of these sections then have individual sub-sections having options on how to define the particular graphic group. Because of this the data entry when editing a graphical element varies considerably depending on the particular section and sub-section that the graphical element belongs to.

Whilst the editing of graphical element properties can be via the template editor, it is more intuitive to do so through the 3d graphical interface by picking the particular graphical element directly. Each graphical element has a ‘hot spot’ adjacent to which is where it must be selected. To identify the hot spot use the status bar at the bottom of the display, which will list a description of the current ‘in range’ element, hard point or other ‘pickable’ feature.

Obviously if an element is not visible it cannot be picked. Refer to the individual visibility switch menu’s Graphics / Enhanced Visibility or use the tree structure set up menu SetUp / Graphics Switches Menu Tree. The other potential issue when trying to pick a graphical element is that its ‘picking’ option may have been turned ‘off’. This is sometimes done to make selecting important features such as hard points easier by turning off the pickabilty of some of the more mundane graphical element types. To check the ‘pick’ status of an element type refer to Graphics / Pick Visibility or the setup box SetUp / Graphics Switches Menu Tree.

The graphical element groups are; Line, Cylinder, Circle, Sphere, Facet, Plane, Distance, Components and Angle. Each of the graphical type sub-sections are discussed under the specific menu section and the relevant overview section.

{bmc bm311.bmp}
Editing a Graphical Elements Properties

A general description of the graphical element properties is given below, (note that when in the graphical edit display you can use the ‘page-up’ and ‘page-down’ keys to move through the graphical elements in the model. The dialogue title bar will indicate the current position and how many are in the model for the selected corner/end.

Graphics Colour,  (choice),  (units -),  (default varies)
Sets the graphics colour for the individual graphical element. Select from the presented choices.

Label,  (string),  (units -),  (default blank)
Sets the Label for the individual graphical element. This is used in menu to aid identifying individual graphical elements of the same type from each other.

Individual graphical element types will require up to four points to define them, un-required points will be ‘greyed’ out.

Point 1,  (choice),  (units -),  (default set by pick)
Defines the first point associated with this graphical element. Select from available points.

Point 2,  (choice),  (units -),  (default set by pick)
Defines the second point associated with this graphical element. Select from available points. Only required for some types.

Point 3,  (choice),  (units -),  (default set by pick)
Defines the third point associated with this graphical element. Select from available points. Only required for some types.

Point 4,  (choice),  (units -),  (default set by pick)
Defines the fourth point associated with this graphical element. Select from available points. Only required for some types.

The next two options will be optionally available depending on not only the specific graphic element type but also the particular points being used. If a hard point is at the connection between two parts, you can choose which of the parts you want the graphic to be associated with. In kinematic mode it makes no difference which part is selected because the two parts are rigidly connected together however in compliance mode you have relative displacement between parts and hence the graphic point will move in relation to the selected part.

P1 Part Position,  (choice),  (units -),  (default set to first)
Optionally defines the part that the first point is associated with. Some points may not have a choice since they may not be at a connection between two parts.

P2 Part Position,  (choice),  (units -),  (default set to first)
Optionally defines the part that the second point is associated with. Some points may not have a choice since they may not be at a connection between two parts.

The next properties, up to a maximum of six, vary in number and variable with each particular graphic type, some of the specifics are discussed below;

P1 Global X Offset,  (real),  (units mm),  (default 0.0 mm)
Defines a global X offset for end 1 of the graphical element from its first point. Similar entries are available for Y and Z.

P2 Global X Offset,  (real),  (units mm),  (default 0.0 mm)
Defines a global X offset for end 2 of the graphical element from its second point. Similar entries are available for Y and Z.

No. of Decimal Points,  (int),  (units -),  (default 0=use default)
Sets the number of decimal points to be used for this graphical element when displaying its value or values. Note that 0 implies use the default settings which for this element type may not be zero, (likely to be three decimal points). To force a zero number of decimal points set the number of decimal points to a negative value.

Radius,  (real),  (units mm),  (default 35.0 mm)
Defines the radius used for some circle and spherical graphical elements.

Length,  (real),  (units mm),  (default 15.0 mm)
Defines the length property for some line, vector and plane graphical elements.

X Vector,  (real),  (units -),  (default 0.0)
For vector lines sets the X component of the vector. Similar entries are given for the Y and Z components of the vector.

+$#>Data Requirements – 3D Bump Stop Data

Bump stops can be optionally included in the model. To add them to your model you will need to pick the two points (on two different parts) that represent the line of action of the bump stop. Note that the points represent the line of action and not the actual position of the two ends. The line of action and the distance defined by the two points is taken as the characteristic start length. Bump stop mechanical properties are then defined as a function force versus the change in length from this characteristic length.

Bump stop properties can thus be split into two sections, the graphical appearance and the mechanical properties.

{bmc bm312.bmp}
Editing the Graphical Appearance of the Bump Stop Element

The graphical properties are;

Static Colour,  (choice),  (units -),  (default dark brown)
Defines the colour of the bump stop at the static position.

Incremental Colour,  (choice),  (units -),  (default light brown)
Defines the colour of the bump stop at any position other than the static case.

Cone Upper Diameter,  (real),  (units mm),  (default 60.0 mm)
Defines the diameter of the upper end of the cone graphic used to visually represent the bump stop element.

Cone Lower Diameter,  (real),  (units mm),  (default 20.0 mm)
Defines the diameter of the lower end of the cone graphic used to visually represent the bump stop element. Note that the graphic will change this diameter as the bump stop starts to become compressed. This diameter change is purely a visual representation of the compression action and does not imply any mechanical or force property.

No. of Radial Facets,  (integer),  (units -),  (default 10)
Defines the number of facets used around the radius for the graphical drawing of this element.

No. of Length Facets,  (integer),  (units -),  (default 5)
Defines the number of facets used along the length for the graphical drawing of this element.

The mechanical properties for the bump stop are accessed by selecting the icon adjacent to the ‘Edit Properties’ label. The mechanical properties for the bump stop are;

The bump stop is defined as a force (N) against distance (mm). Where the X-axis is the distance and the Y-axis is force. To allow for the clearance effect set the force over the initial displacement to be zero and only ramp to a positive value once the bump stop becomes compressed. You can also use a bump stop to represent a rebound stop. Simply define –ve forces at the required –ve travel values. Remember that the X distance values are the change in length between the two bump stop points, not the vertical height change of the wheel.

{bmc bm313.bmp}
Editing the Mechanical properties of the Bump Stop Element

Remember that bump stops are optionally included in the solution. So whilst they might be visible in the model and have associated mechanical properties their effect on the compliant forces could still be disabled. Check the status of menu options Solve / Suspension Bump Stop Preload and Solve / Suspension Bump Stop Rate.

Note: For non-linear bump stops, some resultant forces calculated using the user defined bump stop curve, will be incorrect if the compliant displacements are ‘large’. This is due to the compliant solver linearizing the rate at a certain kinematic position, to compute the force it will apply to the system. Once this force is applied, the compliant displacement if large will change the kinematic position, leading to a new operating point of the bump stop (thus rate change), which is not taken into account to find a new bump stop force. To reduce this effect set the tyre vertical rate to a high value to stop the large displacements.

+$#>Data Requirements – Local Co-ordinate Systems

The default method used to define the position of hard point is the global co-ordinate system. Local co-ordinates systems can be optionally used to define the initial definition position of hard points.

The method for changing a point from using the global co-ordinate system to a local system is, first create the required co-ordinate system then edit the point and switch the points definition co-ordinate system to this new local system.

To create a local co-ordinate system open the dialogue box, Data / Coordinates / Local Coordinate Systems… The ‘add’ button will index the number of co-ordinates systems and allow the definition of this new axis set. The properties for defining a local axis system are listed below;

{bmc bm314.bmp}
Editing the properties of a local co-ordinate system

Label,  (string),  (units -),  (default blank)
Defines the co-ordinate systems label that will be used in the relevant menus.

A co-ordinate system is defined by an origin position, a point on an axis and a point in an appropriate plane. By the use of vector cross products these positions produce the final three axis directions.

Origin Coordinates,  (real),  (units mm),  (default 0.0,0.0,0.0)
The origin co-ordinates can either be defined directly as a global position in x, y and z, this is the ‘Pos’ option, (abbreviation of “Position”).
The second option is to define the origin as being the position of an existing hard point, this is the ‘Pnt’ option, (abbreviation of “Point”).
The third option is a combination of a hard point position and a global offset from this position, this is the ‘Rel’ option, (abbreviation of “Relative”). In this option the defined global offsets are applied to the selected points position to arrive at the net origin position.

Point on Local Axis,  (real),  (units mm),  (default 0.0,0.0,0.0)
First set the axis that will be defined by this point, from either the X, Y or Z axes.
The axis point’s co-ordinates can either be defined directly as a global position in x, y and z, this is the ‘Pos’ option, (abbreviation of “Position”).
The second option is to define the axis point as being the position of an existing hard point, this is the ‘Pnt’ option, (abbreviation of “Point”).
The third option is a combination of a hard point position and a global offset from this position, this is the ‘Rel’ option, (abbreviation of “Relative”). In this option the defined global offsets are applied to the selected points position to arrive at the net axis point’s position.

Point in Local Plane,  (real),  (units mm),  (default 0.0,0.0,0.0)
First set the plane that will be defined by this point, from either the X-Y, X-Z, Y-Z or X-Z planes.
The plane point’s co-ordinates can either be defined directly as a global position in x, y and z, this is the ‘Pos’ option, (abbreviation of “Position”).
The second option is to define the plane point as being the position of an existing hard point, this is the ‘Pnt’ option, (abbreviation of “Point”).
The third option is a combination of a hard point position and a global offset from this position, this is the ‘Rel’ option, (abbreviation of “Relative”). In this option the defined global offsets are applied to the selected points position to arrive at the net plane point position.

{bmc bm315.bmp}
Example screen shot of local co-ordinate system

When a point is switched from one co-ordinate system to another its local co-ordinates are re-calculated in the new co-ordinate system so that no change in absolute position is implied by the change. This is to retain model stability during the transition/redefinition process.

All created co-ordinates systems and their associated definition points can be edited joggled and dragged in the same way as all the other graphical points. Obviously if you change a co-ordinate systems position or orientation any points defined in the is system will have their position modified by this change.

Once a point is switched to being defined by a local co-ordinate system its position in all the editing activities are displayed for this local system. You can continue to drag or joggle it in the normal way. In any results displays (including the status bar) its position will still be listed as in the global axis system.

{bmc bm316.bmp}
Editing a points definition co-ordinate system, selection highlighted

+$#>Results Description – Introduction

This section describes the results variables listed by individual section. For details see sub sections;

2D Results
3D Suspension Derivatives File
3D Points Listing
3D Compliance Coefficients
3D Bush Deflections
3D Joint/Bush Rotations 
3D Bush Forces
AVI File Writer
Unsprung Corner Weights
3D Formatted Point Forces

+$#>Results Description – 2D Results

The 2D results are a reduced set of the 3D derivatives list. The 2D results are normally only viewed through the graphs.

The 2D suspension calculated derivatives for bump/rebound articulations are;

1) Camber Angle
2) Roll Centre Height
3) Track Change

Whilst for 2D roll articulation the calculated derivatives are;

1) Camber Angle
2) Roll Centre Height
3) Roll Centre Lateral

{bmc bm317.bmp}
Typical 2D Results plot

+$#>Results Description – 3D Suspension Derivatives File

The Suspension Derivatives Files (SDF) contains a complete textual listing of the suspension model hard points, calculated static ride values and suspension derivatives varying with each articulation type.

For a definition of each suspension derivative see the Theory section.

The SDF file by default contains the following. Because users can customize the display to create multiple ‘standard’ reports, the actual display may be significantly different:

Listing of input Suspension Hard Points:

	Listing depends on suspension type

Static Values:

	Camber angle (deg): Static wheel camber angle
	Toe Angle (SAE) (deg): Static toe angle, (+ve toe in)
	Toe Angle (Plane of Wheel) (deg): Static toe angle, (+ve toe in)
	Castor Angle (deg): Static Castor angle.
	Castor Trail (Hub Trail) (mm): Static Castor trail.
	Castor Offset (mm): Static Castor offset
	Kingpin Angle (deg): Static Kingpin angle.
	Kingpin Offset (at wheel) (mm): Static Kingpin offset at the wheel centre.
	Kingpin Offset (at ground) (mm): Static kingpin offset at the ground plane.
	Mechanical Trail (mm): Static Mechanical trail.
	Roll Centre Height (mm): Static Roll Centre Height

Derivatives listed for Bump and Rebound Travel:

Camber angle (deg)
Toe Angle (deg)
Castor Angle (deg)
Kingpin angle (deg)
Damper Ratio
Spring Ratio
Anti Dive (%)
Anti Squat (%)
Roll Centre Height to Body (mm)
Roll Centre Height to Ground (mm)
Half Track Change (mm)
Wheelbase change (mm)
Damper Travel (mm)
Spring Travel (mm)

Derivatives listed for Roll Articulation:

Camber angle (deg)
Toe Angle (deg)
Castor Angle (deg)
Kingpin angle (deg)
Damper Ratio
Spring Ratio
Roll Centre Position X (mm)
Roll Centre Position Y (mm)
Roll Centre Position Z (mm)
Half Track Change (mm)
Wheelbase change (mm)
Damper Travel (mm)
Spring Travel (mm)

Derivatives listed for Steer Articulation:

Toe Angle (inner) (deg)
Toe Angle (outer) (deg)
Camber angle (inner) (deg)
Camber Angle (outer) (deg)
Ackermann (%)
Turning Circle Radius (mm)

{bmc bm318.bmp}
Sample Section of the Suspension Derivative File (SDF) listing

+$#>Results Description – 3D Points Listing

The suspension hard points can be listed at any user-defined combination of bump and steering travel.

{bmc bm319.bmp}
Setting the Articulation Position for Points Listing

The point listing display is different depending whether the solver is currently in kinematic or compliant mode. In kinematic mode the Hard point co-ordinates are listed for each hard point for both left and right hand wheels of each axle. Values listed are the X, Y and Z co-ordinates in the global co-ordinate system.

{bmc bm320.bmp}
Kinematic Point Listing

In the compliant mode the Kinematic hard point listing is supplemented at each increment by the inclusion of the compliant hard point positions of each part at the joint. The difference between the kinematic hard point and each compliant parts position at the joint is also listed.

{bmc bm321.bmp}
Compliant Point Listing

All dimensions and deflections are listed in the global Cartesian co-ordinates system, with units of mm.

In addition to points being listed at a user-defined position two other options are available. These are list the co-ordinates of all the points for a selected corner and current calculation position, or list the co-ordinates of a selected single point for all the current calculation positions.

{bmc bm322.bmp}
Point Listing for Single Point at All Positions - bump travel shown

+$#>Results Description – 3D Compliance Coefficients

The 3D compliance coefficients display summarizes the compliant performance of the suspension under a number of defined force sets. Each load case is represented by a series of Vertical bars, each bar being a user selected suspension derivative. The height of the bar is referred to as compliance co-efficient. The displayed co-efficient is the difference between kinematic model and the compliant model, for the selected suspension parameter.

The sign reflects the direction of the change in the suspension parameter, i.e. a co-efficient of –0.1 for camber indicates that the camber angle has an increase in negative camber of 0.1 due to the bush compliances under this external load set.

Compliance co-efficients are calculated for the ‘ride’ condition only, (tip, to view at an alternative position, use the Set Ride Height function).

{bmc bm323.bmp}
Example 3D Compliance Coefficients Display

+$#>Results Description – 3D Bush Deflections

The 3D bush deflections listing is only available for compliant models. Calculated deflections are listed for each bushed suspension hard point at each articulation increment and for each articulation type. The bush deflections are listed for the currently displayed external force set and suspension spring setting. Only hard point that are ‘bushed’ will appear in the list. The deflection is the difference between the kinematic position and the compliant position. Note the sign of the deflections is a function of which part is considered to move relative to what. If in doubt check the deformed geometry plot to identify relative sign.

Points are listed labeled by template point No.

Results Given are;

DX Global, (N): Lists the bush deflection component in the global X-axis.

DY Global, (N): Lists the bush deflection component in the global Y-axis.

DZ Global, (N): Lists the bush deflection component in the global Z-axis.

DX Local, (N): Lists the bush deflection component in the local X-axis.

DY Local, (N): Lists the bush deflection component in the local Y-axis.

DZ Local, (N): Lists the bush deflection component in the local Z-axis.

{bmc bm324.bmp}
Example 3D Bush Deflections Listing

+$#>Results Description – 3D Joint/Bush Rotations

The 3D joint/bush rotations listing is only available for compliant models. Calculated rotations are listed for each suspension hard point at each articulation increment and for each articulation type. The bush rotations are the kinematic values that are used to determine bush pre-loads when included. The extra rotations due to compliance are not listed.

Points are listed labeled by template point No.

Results Given are;

DX Global, (N): Lists the joint/bush rotation component in the global X-axis.

DY Global, (N): Lists the joint/bush rotation component in the global Y-axis.

DZ Global, (N): Lists the joint/bush rotation component in the global Z-axis.

DX Local, (N): Lists the joint/bush rotation component in the local X-axis.

DY Local, (N): Lists the joint/bush rotation component in the local Y-axis.

DZ Local, (N): Lists the joint/bush rotation component in the local Z-axis.

{bmc bm325.bmp}
Example 3D Joint/Bush Rotations Listing

+$#>Results Description – 3D Bush Forces

The 3D bush forces listing is only available for compliant models. Calculated forces are listed for each suspension hard point at each articulation increment and for each articulation type. The bush forces are listed for the currently displayed external force set and suspension spring setting. Each hard point is listed irrespective of whether set as ‘rigid’ or ‘bushed’.

Points are listed labeled by template point No.

Results Given are;

FX Global, (N): Lists the bush force component in the global X-axis.

FY Global, (N): Lists the bush force component in the global Y-axis.

FZ Global, (N): Lists the bush force component in the global Z-axis.

FX Local, (N): Lists the bush force component in the local X-axis.

FY Local, (N): Lists the bush force component in the local Y-axis.

FZ Local, (N): Lists the bush force component in the local Z-axis.

{bmc bm326.bmp}
Example 3D Bush Forces Listing

+$#>Results Description – AVI File Writer

The graphics display animation sequences can be saved to a file. Currently only AVI format is supported, and without compression. A number of options are presented to make creating AVI files a simple task. Files can be created based on a the current motion sequence, i.e. bump, roll, steering or combined, or via a sequence of user selected images.

{bmc bm327.bmp}
AVI File Writer Dialogue Box

The top portion of the display identifies whether the AVI file is to be created from the 'Current Motion Sequence' or from a series of 'Stills'. If using the Current motion sequence option, simply select the 'Write File' option to identify the file name/location to save the AVI file too. The AVI file is then generated.

To create an AVI from a sequence of stills set the option to 'create from stills' then select the 'start' button. This will enable the 'Grab' button and zero the 'frames' counter. You can now set the required graphics view and then 'grab' it. Repeat this process until you have grabbed all required frames and then select 'End' to indicate the end of the grab sequence and enable the 'Save File…' option. Notice that grabbed images can be viewed as an editable list for a limited amount sorting, editing and deletion prior to writing the file.

{bmc bm328.bmp}
Editing the 'Grabbed' Stills list

Within the stills list display users can view individual frames for editing. The application used to do this is identified in the 'BMP use' option at the bottom of the main AVI file writer dialogue.

Both the AVI sequence writer option and the stills grabber option can be either for the complete graphics screen or a selected area. The screen area is defined via clip rectangle the settings for which can either be entered directly or picked via the mouse. A switch is provided to optionally show the clip region on the graphics screen.

{bmc bm329.bmp}
Screen Clip Area Selected

By default the AVI file will include a single copy of the sequence. The user can change the number of cycles that are written to the AVI file. In the case of a user picked sequence of stills they would be repeated n cycle times. The replay rate of the AVI file is set by default to replay at a rate of 10 frames/sec. The user can change this setting prior to creating the file.

A second file write option is provided principally for user grabbed sequences to append the grabbed stills but in reverse order to the AVI file. This then provides a smooth animation sequence from start to end and back to start again when looping through, without having to pick a full sequence.

The AVI file can be viewed automatically after writing by having the 'Open AVI in viewer after Write/Save' option checked. The AVI will be viewed using the application identified in the Windows registry as being the default AVI file viewer. This can be specified directly by the user through 'AVI Use'; setting.

+$#>Results Description – Unsprung Corner Weights

In compliance mode if the part mass properties are correctly defined, (mass and position), the unsprung corner weights can be calculated by applying a gravity force and determining the change in force in the tyre vertical force. This is performed automatically using the Results / Unsprung Corner Weights menu option.

{bmc bm330.bmp}
Unsprung Corner Weight Results Display

The option is given to locally access and edit the current parts mass property. If you change a part mass property use the update button to refresh the calculation.

Full access to the parts mass properties is through the Data / Mass Data / C of G Properties. Alternatively the properties can be accessed by picking the relevant C of G symbol. These are only visible in compliant mode and are subject to their own individual visibility switch, Graphics / Part C of G Visibility / C of G Marker.

+$#>Results Description – 3D Formatted Point Forces

In addition to the standard bush forces results display, the user can create a line by line formatted point force display. The display is a defined mixture of tables, columns and lines. Thus you define how many tables, for each table how many columns and the column properties, finally the no of lines and the properties of each line.

{bmc bm331.bmp}
Example formatted point forces screen shot

The format settings are stored under a specific slot number, (0-25). Each setting is editable and saved to the INI file. To edit an individual setting change the display to the required slot, Setting / Select required No. and then use the local menu Display / Edit Current Settings. 

Each property is discussed below.

Label,  (string),  (units -),  (default blank)
Defines the label used to identify the setting in any relevant menu entry or dialogue box heading.

No. of Tables,  (integer),  (units -),  (default 0)
Sets the number of separate tables to include for the current setting, (maximum 10).

At the top of the display before the first table is an optional header. The visibility for this header is made up of five individual parts.

Data Echo,  (choice),  (units -),  (default On)
Optionally includes a copy of the defined hard point coordinates.

Time / Date,  (choice),  (units -),  (default On)
Optionally includes the time a date that the display was produced.

Analysis Type,  (choice),  (units -),  (default On)
Optionally includes a text line that identifies the motion type used for the analysis.

Corner,  (choice),  (units -),  (default On)
Optionally includes a text line that the corner/end that the results are displayed for.

Template Type,  (choice),  (units -),  (default On)
Optionally includes a text line that identifies the template type of the corner/end used in the model for these results.

The following properties are defined for each individual table;

Table Heading,  (string),  (units -),  (default blank)
Defines the string used as a heading for the table.

No. of Columns,  (integer),  (units -),  (default 0)
Defines the number of columns used for the table. Each columns represents a potential location to list a results. Note that columns can be left empty to aid visual appearance and readability.

Column Size,  (integer),  (units -),  (default 10)
Defines the character width used for each column. Each column has to use the same width so set this to be as wide as is required.

No. of Col. Header Lines,  (integer),  (units -),  (default 4)
Sets the number of lines used for the header of the columns. Column header strings are clipped to the defined width and then split on to the next line of the column header. Column header labels are taken from the columns parameter description.

No. of Lines,  (integer),  (units -),  (default 0)
Sets the number of results lines to be used in the table. Each line can be individually controlled in terms of point and force type, whilst the column controls which load case to be used.

Comment Size,  (integer),  (units -),  (default 0)
Each line has an optional comment string added to the front of the line. This sets the space allocated for the comment as a maximum number of character spacings. Comments that are longer than this will be clipped to length.

The following properties are defined for each individual column;

Load Case,  (choice),  (units -),  (default User Definable Default Set)
Sets the load case to use for each particular column. Selection is made from the available defined sets.

Decimal Points,  (integer),  (units -),  (default 0)
Sets the number of decimal points used for each column.

The following properties are defined for each individual line;

End,  (choice),  (units -),  (default none)
Sets the suspension end to use for the specific line.

Point,  (choice),  (units -),  (default not set)
Sets the hard point to use from the current ‘ends’ list. The list also includes the Tyres, Springs and Bump Stops.

Force,  (choice),  (units -),  (default not set)
Identifies the force to use for this Line, Select from Local x, y and Z, Global x, y and z or the resultant.

Articulation,  (choice),  (units -),  (default As Set)
Set which displacement module to use, from ‘As Set’, bump/rebound, roll or steering. ‘As Set’ implies the current selected articulation mode.

Position,  (choice),  (units -),  (default no set)
Set which position for the selected displacement mode to use. This list will be a function of the currently selected displacement in the preceding column.

Comment,  (string),  (units -),  (default none)
Define the optional comment for a line. Comments are placed at the beginning of the line in the space defined in the earlier ‘comment size’ setting.

{bmc bm332.bmp}
Editing the Format settings

+$#>How To – Customize SDF Display Settings

Introduction  

With the Formatted SDF results users have full format control over both the values displayed and the layout format, each format is stored in a numbered and labelled slot. The first four slots 0,1,2 and 3 have a hard coded format setting, these can be overwritten by settings in the INI file, that relate to each of the four default displacement modes. The four hard-coded format settings are set up to mimic the original fixed format version outputs of each displacement mode.

Each format slot is selected via the local ‘Setting’ menu. This lists the available format settings. Note that by default empty undefined slots are labelled as ‘Not Defined’. A local switch independent of the format controls which end(s) are plotted.

To change the setting of a format set, first via the ‘Setting’ menu select the required format slot number. Now open the format editor via the local Display / Edit Current Setting’ menu.

Each setting display is made up a number of tables, each table having a defined number of columns. Each column then has its own definition of variable and display properties.

{bmc bm333.bmp}
Editing the SDF Display Format

The properties used within each individual ‘setting’ are;

Label,  (string),  (units -),  (default “Not Defined”)
Sets the label used to identify each individual setting. This is used in any relevant menus and dialogue box titles.

No. of Tables,  (integer),  (units -),  (default 0)
Defines how many tables are to be used to create this settings display. Each table will have its own column properties.

At the top of the display before the first table is an optional header. The visibility for this header is made up of five individual parts.

Data Echo,  (choice),  (units -),  (default On)
Optionally includes a copy of the defined hard point coordinates.

Time / Date,  (choice),  (units -),  (default On)
Optionally includes the time a date that the display was produced.

Analysis Type,  (choice),  (units -),  (default On)
Optionally includes a text line that identifies the motion type used for the analysis.

Corner,  (choice),  (units -),  (default On)
Optionally includes a text line that the corner/end that the results are displayed for.

Template Type,  (choice),  (units -),  (default On)
Optionally includes a text line that identifies the template type of the corner/end used in the model for these results.

The following properties are defined for each individual table;

Table Heading,  (string),  (units -),  (default blank)
Defines the text string displayed above the table.

No. of Columns,  (integer),  (units -),  (default 0)
Defines the number of columns used for the table. Each columns represents a potential location to list a results. Note that columns can be left empty to aid visual appearance and readability.

Column Size,  (integer),  (units -),  (default 10)
Defines the character width used for each column. Each column has to use the same width so set this to be as wide as is required.

No. of Col. Header Lines,  (integer),  (units -),  (default 4)
Sets the number of lines used for the header of the columns. Column header strings are clipped to the defined width and then split on to the next line of the column header. Column header labels are taken from the columns parameter description.

The following properties are defined for each individual column;

Source,  (choice),  (units -),  (default ‘Not Set’)
Defines the origin type of the parameters list to be used for the data source. Options are, ‘Not Set’, ‘Std. SDF’, ‘Front Graphic’. ‘Rear Graphic’ and ‘User SDF’.

Parameter,  (choice),  (units -),  (default ‘Not Set’)
Defines the specific parameter to use in the column. The contents of the list depends on the setting used for the ‘Source’ variable above.

Decimal Points,  (integer),  (units -),  (default 0)
Defines the number of decimal points used in the listing of the columns variable.

Corner,  (integer),  (units -),  (default As Set)
Specifies which corner is listed in the column. The default option of ‘As Set’ implies that the values will be for the prescribed corner. The options of –1, +1, +2 and +3 allow you to generate a display that lists in adjacent columns the parameter for both left and right hand wheel, or indeed all four wheels.

+$#>How To – Create User Defined Results

Introduction  

User defined results allows users to create their own specific analysis results but building equations that can use combinations of standard results, calculated forces, point displacements, mathematical operators and standard parameters. These user defined results are then available to plotted and listed in the same way as the standard results. User defined results can also be used in the equation for another user defined results.

The equations are built up in a character string that uses a simplified Fortran language style. Within these strings existing results and point positions are identified by a combination of the square brackets ‘[‘ and ‘]’ together with a standard sequence of characters. Thus the use of square brackets in any implementation of the user language should be avoided.

The standard results that can be used within user results are given in eighteen different sections. Whilst you don’t need to type these in yourself as you can use the ‘insert’ buttons supplied.

Standard SDF’s, identified by square brackets and the standard SDF string, i.e. [Camber angle], for the static value append a ‘0’ within the last square bracket, i.e. [Camber Angle0].

User SDF’s, identified by square brackets and the user SDF string with a preceding ‘U’, i.e. [Umysdf], for the static value append a ‘0’ within the last square bracket, i.e. [Umysdf0].

Front Pnt by Label, identified by square brackets and the points long label. You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [Lower wishbone front pivotX] for the x co-ordinate of the point or [Lower wishbone front pivotV] for the vector position of the point. For the static value append a ‘0’ within the last square bracket, i.e. [Lower wishbone front pivotX0].

Rear Pnt by Label, (this is identical in form to the preceding section), identified by square brackets and the points long label. You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [Lower wishbone front pivotX] for the x co-ordinate of the point or [Lower wishbone front pivotV] for the vector position of the point. For the static value append a ‘0’ within the last square bracket, i.e. [Lower wishbone front pivotX0].

Front Pnt by No., identified by square brackets and the point’s position in the template, (note this is not the same as the numeric short string, see later sections). You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [frontP1X] for the x co-ordinate of the point or [frontP1V] for the vector position of the point. For the static value append a ‘0’ within the last square bracket, i.e. [frontP1X0].

Rear Pnt by No., identified by square brackets and the point’s position in the template, (note this is not the same as the numeric short string, see later sections). You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [rearP1X] for the x co-ordinate of the point or [rearP1V] for the vector position of the point. For the static value append a ‘0’ within the last square bracket, i.e. [rearP1X0].

Front Pnt by Short Label, identified by square brackets and the points short label. You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [frontS1X] for the x co-ordinate of the point or [frontS1V] for the vector position of the point. For the static value append a ‘0’ within the last square bracket, i.e. [frontS1X0].

Rear Pnt by Short Label, identified by square brackets and the points short label. You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [rearS1X] for the x co-ordinate of the point or [rearS1V] for the vector position of the point. For the static value append a ‘0’ within the last square bracket, i.e. [rearS1X0].

Front Graphic, identified by square brackets a simple ‘frontG’ and the graphics number. Only one property is assumed available for each graphical element, it normally being a ‘distance’, a typical entry would look like [frontG3], whilst the for the static value append a ‘0’ within the last square bracket, i.e. [frontG30]. Some care may need to taken when trying to use the extra ‘0’ for static since this may also imply an alternative graphic position, i.e. graphic 10 and graphic 1 static.

Rear Graphic, identified by square brackets a simple ‘rearG’ and the graphics number. Only one property is assumed available for each graphical element, it normally being a ‘distance’, a typical entry would look like [rearG2], whilst the for the static value append a ‘0’ within the last square bracket, i.e. [rearG20]. Some care may need to taken when trying to use the extra ‘0’ for static since this may also imply an alternative graphic position, i.e. graphic 10 and graphic 1 static.

Front force by label, identified by square brackets, the points long label and either FX, FY, FZ or FR, for the x, y, z, or resultant force at the specified point, i.e. [Lower Wishbone Front PivotFX]. No static value option is currently supported.

Rear force by label, identified by square brackets, the points long label and either FX, FY, FZ or FR, for the x, y, z, or resultant force at the specified point, i.e. [Lower Wishbone Front PivotFX]. No static value option is currently supported. Note that this method does not specifically define a front or rear suspension. It is implied by the point label itself and relies on it only being found in the required ends template. If you are using the same template for both ends you cannot use this non-end specific method unless it can also be applied to the front. Instead use one the following methods. No static value option is currently supported.

Front Force by No., identified by square brackets and the point’s position in the template, (note this is not the same as the numeric short string, see later sections). You identify either an individual force component by appending the ‘FX’, ‘FY’ or ‘FZ’ characters or an ‘FR’ if you want to use the resultant force, i.e. [frontP1FX] for the x force of the point or [frontP1FR] for the resultant force at the point. No static value option is currently supported.

Rear Force by No., identified by square brackets and the point’s position in the template, (note this is not the same as the numeric short string, see later sections). You identify either an individual force component by appending the ‘FX’, ‘FY’ or ‘FZ’ characters or an ‘FR’ if you want to use the resultant force, i.e. [rearP1FX] for the x force of the point or [rearP1FR] for the resultant force at the point. No static value option is currently supported.

Front Force by Short Label, identified by square brackets and the points short label. You identify either an individual force component by appending the ‘FX’, ‘FY’ or ‘FZ’ characters or an ‘FR’ if you want to use the resultant force, i.e. [frontS1FX] for the x component force or [frontS1FR] for the resultant force at the point. No static value option is currently supported.

Rear Force by Short Label, identified by square brackets and the points short label. You identify either an individual force component by appending the ‘FX’, ‘FY’ or ‘FZ’ characters or an ‘FR’ if you want to use the resultant force, i.e. [rearS1FX] for the x component force or [rearS1FR] for the resultant force at the point. No static value option is currently supported.

Front Pnt by Type., identified by square brackets a preceding ‘T’ and a specific point type label, (note this type label does not directly imply end so can be applied to both front and rear). You identify either an individual component by appending the ‘X’, ‘Y’ or ‘Z’ character or a ‘V’ if you want to use the point within a vector equation, i.e. [TWheel centreX] for the x co-ordinate of the wheel centre or [Twheel centreV] for the vector position of the wheel centre. For the static value append a ‘0’ within the last square bracket, i.e. [Twheel centreX0].

Parameters, identified by square brackets a preceding ‘P’ and the parameter description string, i.e. [Pbump Travel (mm)]. You can also use the parameter number, i.e. [P1]. Currently 30 parameters are available, (see below);

	  1 Bump Travel (mm)
	  2 Rebound Travel (mm)
	  3 Bump Rebound Increment (mm)
	  4 Roll Angle (deg)
	  5 Roll Increment (deg)
	  6 Steer Travel (mm)
	  7 Steer Increment (mm)
	  8 Wheelbase (mm)
	  9 C of G Height (mm)
	10 Braking Front (%)
	11 Drive Front (%)
	12 Total Weight Front (%)
	13 Front Brake Type (1 = Inboard 2 = Outboard)
	14 Rear Brake Type (1 = Inboard 2 = Outboard)
	15 Total Sprung Weight (kg)
	16 Front Type (1 = Independent 2 = Rigid )
	17 Rear Type (1 = Independent 2 = Rigid )
	18 Drive Shaft Joint (Tulip) Radius (mm)
	19 Rack Pinon Gear Radius (mm)
	20 Tyre Rolling Radius (mm)
	21 Tyre Width (mm)
	22 Tyre Vertical Stiffness (N/mm)
	23 Spring 1 Rate (N/mm)
	24 Spring 1 Free Length (mm)
	25 Spring 1 Fitted Length (mm)
	26 Spring 2 Rate (N/mm)
	27 Spring 2 Free Length (mm)
	28 Spring 2 Fitted Length (mm)
	29 Damper 1 Rate (N.s/mm)
	30 Damper 2 Rate (N.s/mm)

Available maths functions are given in the right hand selection box. To include into the function string at the currently selected position select the required function from the right hand box and select the ‘Insert Func’.

The supporting maths functions in the user SDF' are;
-    	Subtract two numbers, as in A - B
*    	Multiply two numbers, as in A * B
**	Raise to the power of , as in A**2
/	Divide two numbers, as in A / B
+	Add two numbers, as in A + B
ABS	Returns the absolute value, as in ABS(A)
ACOS	Returns the arc cosine of an angle with the returned angle in radians, as in ACOS(A)
ACOSD	Returns the arc cosine of an angle with the returned angle in degrees, as in ACOSD(A)
ASIN	Returns the arc sine of an angle with the returned angle in radians, as in ASIN(A)
ASIND	Returns the arc sine of an angle with the returned angle in degrees, as in ASIND(A)
ATAN	Returns the arc tan of an angle with the returned angle in radians, as in ATAN(A)
ATAND	Returns the arc tan of an angle with the returned angle in degrees, as in ATAND(A)
COS	Returns the cosine of an angle with the angle in radians, as in COS(A)
COSD	Returns the cosine of an angle with the angle in degrees, as in COSD(A)
COSH	Returns the hyperbolic cosine of an angle with the angle in radians, as in COSH(A)
EXP	Returns the exponential, as in EXP(A)
INT	Returns integer of argument, as in INT(A)
LOG	Returns natural logarithm, as in LOG(A)
LOG10	Returns common logarithm to base 10, as in LOG10(A)
NINT	Returns nearest integer of the argument, as in NINT(A)
REAL	Returns real number for integer argument, as in REAL(A)
SIN	Returns the sine of an angle with the angle in radians, as in SIN(A)
SIND	Returns the sine of an angle with the angle in degrees, as in SIND(A)
SINH	Returns the hyperbolic sine of an angle with the angle in radians, as in SINH(A)
SQRT	Returns the square root of the argument, as in SQRT(A)
TAN	Returns the tan of an angle with the angle in radians, as in TAN(A)
TAND	Returns the tan of an angle with the angle in degrees, as in TAND(A)
TANH	Returns the hyperbolic tan of an angle with the angle in radians, as in TANH(A)
VCROSS Returns as a vector the cross product of two vector arguments, as in VCROSS(vA,vB)
VDOT Returns as a scalar the dot product of two vector arguments, as in VDOT(vA,vB)
VMAG Returns as a scalar the magnitude of a vector argument, as in VMAG(vA)
VNORM Returns a unitized vector of the vector argument, as in VNORM(vA)

All these individual point, force, parameter and maths function can be freely mixed to produce the required equation and result. Some simple examples are given below to illustrate the points;

The ratio of castor angle to kingpin angle;
           [Castor Angle]/[Kingpin Angle]

The castor angle change;
           [Castor Angle]-[Castor Angle0]

The distance between two points (note extensive use of ABS to ensure stability);
           SQRT(  (ABS([frontP3X]-[frontP5X]))**2.0
                     + (ABS([frontP3Y]-[frontP5Y]))**2.0
                     + (ABS([frontP3Z]-[frontP5Z]))**2.0 )
(as a test you can compare this against a graphical plot of the distance between two points added as a graphical)

The ratio of the X force to the resultant force at a point.
           [Lower wishbone front pivotFX]/[Lower wishbone front pivotFR]

Using an earlier user function (No. 1) in a later user function
           2.0*[U1]*COSD([Camber Angle])

+$#>How To – Use Controls

Implementation of Simple Position/Link Length control elements to Shark

Objective:  To allow the user to define a kinematic suspension model that can have either/or moving hard point(s) and changing link length(s). These changes to occur as a function of a measured displacement(s). This model change is applied automatically by the software as part of its solution iteration.

Implementation:  The required displacements are identified. Each 'displacement transducer' is defined by its two end points. Additional points can/may need to be added to a template to represent the desired transducer positions.  The desired variable length links are 'tagged', being identified by their two end points.  The desired moving hard points are marked, and their translating direction identified by global vector components, (dx,dy,dz).

{bmc bm334.bmp}
Example screen shot showing transducer and actuator

A spline is used to equate the change in transducer length to the change in link length, or change in hard point position. The spline can be interactively edited to review the change in the spline data has on displayed SDF graphs. The spline data would be of the form, x-axis is change in transducer length from static, y-axis enforced change in link length or point position.

{bmc bm335.bmp}
Example Screen Shot of Spline Editor

+$#>Theory – Definition of Suspension Derivatives

Introduction  

A large number of ‘suspension derivatives’ are calculated by ‘SHARK’, some are given at the static ride height only, whilst the variation with articulation is determined for others. The definition of these derivatives is given in this section and are based upon the SAE standard ‘Vehicle Dynamics Terminology’ SAE J670e. Where variations from this standard exist or where specific Lotus standards have been applied these will be identified. The units used together with the sign convention are also stated. The calculation formulae are given in terms of both the Shark co-ordinate system and point numbering system.

Static Values

Camber Angle, (deg)
The inclination of the wheel plane to the vertical. It is considered positive when the wheel leans outward at the top and negative when it leans inward.

{bmc bm336.bmp}
Camber Angle Definition

Toe Angle, SAE, (deg)
The static toe angle of a wheel at a specified wheel load or relative position of the wheel centre with respect to the sprung mass, is the angle between a longitudinal axis of the vehicle and the line of intersection of the wheel plane and the road surface. The wheel is ”toed-in” if the forward portion of the wheel is turned towards a central longitudinal axis of the vehicle (+ve), and “toed-out” if turned away, (-ve).

Toe Angle, Plane of Wheel, (deg)
This derivative is a Lotus definition which has the same units and sign convention as the SAE term, but instead of using the intersection of the wheel plane to the ground as the toe line, the angle is measured in the plane of the wheel.

{bmc bm337.bmp}
Toe Angle Definitions

Castor Angle, (deg)
The angle in side elevation between the steering axis and the vertical. It is considered positive when the steering axis is inclined rearward (in the upward direction), and negative when the steering axis is inclined forward.

Castor Trail, hub trail, (mm)
The horizontal distance in side elevation between the steering axis and the wheel centre. The offset is considered positive when the wheel centre is forward of the steering axis and negative when it is rearward.

Castor Offset, (mm)
The distance in side elevation between the point where the steering axis intersects the ground, and the centre of tyre contact. The offset is considered positive when the intersection point is forward of the tyre contact centre and negative when it is rearward.

{bmc bm338.bmp}
Castor Angle and Offset Definitions

Kingpin Angle, (deg)
The angle in front elevation between the steering axis and the vertical. It is considered positive when the steering axis leans inwards at the top and negative when it leans out.

Kingpin offset, at wheel, (mm)
Kingpin offset at the wheel centre is the horizontal distance in front elevation from the wheel centre to the steering axis. It is considered positive when the wheel centre is outboard of the steering axis, (normal case), and negative if inboard.

Kingpin offset, at ground, (mm)
Kingpin offset at the ground is the horizontal distance in front elevation between the point where the steering axis intersects the ground and the centre of the tyre contact. It is considered positive when the tyre contact is outboard of the steering axis intersection and negative if inboard.

Mechanical Trail, (mm)
The perpendicular distance in side elevation between the steering axis and the centre of tyre contact. It is considered positive when the steering axis is forward of the tyre contact centre and negative when it is rearward.

{bmc bm339.bmp}
Kingpin Angle and Offset Definitions

Roll Centre Height, (mm)
The point in the transverse vertical plane through any pair of wheel centres at which lateral forces may be applied to the sprung mass without producing suspension roll. The preceding is the SAE definition, and is more normally stated as ‘the instantaneous centre of rotation of the body’. At static for a symmetrical suspension this point lies on the vehicle centreline and thus only the roll centre height is quoted at static. The calculation procedure uses a small bump step to define the tyre contact patch path, and allows a perpendicular plane to be constructed to this path at the current contact point. The intersection of this plane with either the other sides plane, (roll), or the vehicle centre line, (bump) defines the roll centre position.

{bmc bm340.bmp}
Roll Centre Height Definition

Incremental Values, (Included in SDF formatted file)

Camber Angle, (deg)
The inclination of the wheel plane to the vertical. It is considered positive when the wheel leans outward at the top and negative when it leans inward.

Toe Angle, SAE, (deg)
The static toe angle of a wheel at a specified wheel load or relative position of the wheel centre with respect to the sprung mass, is the angle between a longitudinal axis of the vehicle and the line of intersection of the wheel plane and the road surface. The wheel is ”toed-in” if the forward portion of the wheel is turned towards a central longitudinal axis of the vehicle (+ve), and “toed-out” if turned away, (-ve).

Toe Angle, Plane of Wheel, (deg)
This derivative is a Lotus definition which has the same units and sign convention as the SAE term, but instead of using the intersection of the wheel plane to the ground as the toe line, the angle is measured in the plane of the wheel.

Castor Angle, (deg)
The angle in side elevation between the steering axis and the vertical. It is considered positive when the steering axis is inclined rearward (in the upward direction), and negative when the steering axis is inclined forward.

Kingpin Angle, (deg)
The angle in front elevation between the steering axis and the vertical. It is considered positive when the steering axis leans inwards at the top and negative when it leans out.

Damper Ratio
The ratio of change in the vertical height of the tyre contact centre and the change in length of the damper. It has no sign convention and would be greater than one when the change in vertical height of the wheel is more than the change in length of the damper. (Lotus definition).

Spring Ratio
The ratio of change in the vertical height of the tyre contact centre and the change in length of the spring. It has no sign convention and would be greater than one when the change in vertical height of the wheel is more than the change in length of the spring. (Lotus definition).

Anti Dive, (%)
The ratio, given as a percentage, of the amount of the weight transfer under breaking that is reacted by the suspension geometry in resisting the body pitching motion. Thus 100% anti-dive results in no theoretical body pitching under braking. The construction technique relies on the suspension side view instantaneous centre being found and then further construction using brake split and vehicle c of g height. (Lotus Definition). Side view instantaneous centres (I.C.) are determined using small perturbation and projecting a normal to the path of the tyre contact point. Note that the origin point changes depending whether braking is inboard or outboard.

{bmc bm341.bmp}
% Anti-Dive Derivation

Anti Squat, (%)
The ratio, given as a percentage, of the amount of the weight transfer under acceleration that is reacted by the suspension geometry in resisting the body pitching motion. Thus 100% anti-squat results in no theoretical body pitching under acceleration. The construction technique relies on the suspension side view instantaneous centre being found and then further construction using torque split and vehicle c of g height.. (Lotus Definition). Side view instantaneous centres (I.C.) are determined using small perturbation and projecting a normal to the path of the tyre contact point. The value is only applicable to axles with some portion of the drive load. Note that the origin position changes depending on whether the suspension is independent or not.

{bmc bm342.bmp}
% Anti-Squat Derivation – 4WD

{bmc bm343.bmp}
% Anti-Squat Derivation - FWD

Roll Centre Height to Body, (mm)
The point in the transverse vertical plane through any pair of wheel centres at which lateral forces may be applied to the sprung mass without producing suspension roll. The preceding is the SAE definition, and is more normally stated as ‘the instantaneous centre of rotation of the body’. At static for a symmetrical suspension this point lies on the vehicle centreline and thus only the roll centre height is quoted at static. This is the variation of the roll centre height with wheel bump/rebound articulation, relative to the body origin. (Lotus definition).

Roll Centre Height to Ground, (mm)
See full description above. This is the variation of the roll centre height with wheel bump/rebound articulation, relative to the ground origin. (Lotus definition).

Half Track Change, (mm)
The change in cross car co-ordinates from the static condition of the tyre contact centre. It is considered positive when the change is an increase the track and negative for a decrease in track. (Lotus definition).

Wheelbase Change, (mm)
The change in fore/aft car co-ordinates from the static condition of the tyre contact centre. It is considered positive when the change is an increase in the wheelbase and negative for a decrease in wheelbase. (Lotus definition).

Damper Travel, (mm)
The change in distance from the static condition between the two points defining the damper attachment points. It is considered positive when the change is such as to increase the distance between them and negative when it decreases. (Lotus definition).

Spring Travel, (mm)
The change in distance from the static condition between the two points defining the spring attachment points. It is considered positive when the change is such as to increase the distance between them and negative when it decreases. (Lotus definition).

Roll Centre Position, X, (mm)
The incremental X co-ordinate of the roll centre under roll articulation. (Lotus Definition)

Roll Centre Position, Y, (mm)
The incremental Y co-ordinate of the roll centre under roll articulation, normally given the wheel centre value. (Lotus Definition)

Roll Centre Position, Z, (mm)
The incremental Z co-ordinate of the roll centre under roll articulation. (Lotus Definition)

Ackermann, (%)
The ratio, given as a percentage, of the actual steer angles compared to those required for zero scrub. (Lotus Definition)

{bmc bm344.bmp}
% Ackermann Definition

Additional Incremental Values, (Available on Graphs or SDF splines file)

Castor Trail,  (mm)
The horizontal distance in side elevation between the steering axis  and the wheel centre. The offset is considered positive when the steering axis is forward of the wheel centre and negative when it is rearward.

Castor Offset, (mm)
The distance in side elevation between the point where the steering axis intersects the ground, and the centre of tyre contact. The offset is considered positive when the intersection point is forward of the tyre contact centre and negative when it is rearward.

Kingpin offset, at wheel centre, (mm)
Kingpin offset at the wheel centre is the horizontal distance in front elevation from the wheel centre to the steering axis. It is considered positive when the wheel centre is outboard of the steering axis, (normal case), and negative if inboard.

Kingpin offset, at ground, (mm)
Kingpin offset at the ground is the horizontal distance in front elevation between the point where the steering axis intersects the ground and the centre of the tyre contact. It is considered positive when the tyre contact is outboard of the steering axis intersection and negative if inboard.

Mechanical Trail, (mm)
The perpendicular distance in side elevation between the steering axis and the centre of tyre contact. It is considered positive when the steering axis is forward of the tyre contact centre and negative when it is rearward.

TCP Position, X, (mm)
The incremental X co-ordinate of the tyre contact point.

TCP Position, Y, (mm)
The incremental Y co-ordinate of the tyre contact point.

TCP Position, Z, (mm)
The incremental Z co-ordinate of the tyre contact point.

Hub Position, X, (mm)
The incremental X co-ordinate of the wheel centre point.

Hub Position, Y, (mm)
The incremental Y co-ordinate of the wheel centre point.

Hub Position, Z, (mm)
The incremental Z co-ordinate of the wheel centre point.

Tyre Vertical Force, (N)
The incremental value of the vertical force at the tyre contact point. Only given in compliant mode.

Swing Arm Length {Front}, (mm)
The incremental length of the front view virtual swing arm.

Swing Arm Centre Y {Front}, (mm)
The incremental Y position of the front view virtual swing arm centre.

Swing Arm Centre Z {Front}, (mm)
The incremental Z position of the front view virtual swing arm centre.

{bmc bm345.bmp}
Front View Swing Arm Definitions

Swing Arm Length {Side}, (mm)
The incremental length of the side view virtual swing arm.

Swing Arm Centre X {Side}, (mm)
The incremental X position of the side view virtual swing arm centre.

Swing Arm Centre Z {Side}, (mm)
The incremental Z position of the side view virtual swing arm centre.

Roll Centre Height to Body, (mm)
The point in the transverse vertical plane through any pair of wheel centres at which lateral forces may be applied to the sprung mass without producing suspension roll. The preceding is the SAE definition, and is more normally stated as ‘the instantaneous centre of rotation of the body’. At static for a symmetrical suspension this point lies on the vehicle centreline and thus only the roll centre height is quoted at static. This is the variation of the roll centre height with wheel bump/rebound articulation, relative to the body origin. (Lotus definition).

Roll Centre Height to Ground, (mm)
See full description above. This is the variation of the roll centre height with wheel bump/rebound articulation, relative to the ground origin. (Lotus definition).

TCP dx/dz Gradient, (mm/mm)
The incremental value for the gradient of the Tyre contact point when viewed from the side.

Turning Circle Radius, (mm)
The incremental turning circle is calculated from the average intersection point of the steered front wheel normals at the rear axle line.

{bmc bm346.bmp}
Turning Circle Definition

+$#>Theory – The Two Part Steering Rack Model

Description:

The two-part rack adds two new parts, the “Rack Link” and the “Rack Body”. The rack link slides within the rack body through two connections that are tagged in the template as ‘Rack Mount Point’ and ‘Rack Lateral Mount Point’. Being tagged the solver automatically applies suitable stiffness numbers to them to replicate sliders. The ‘rack lateral stiffness’ is applied to the one tagged as the Lateral mount point. The rack body is then connected to ground through two further bush connections, which if undefined, are set to the ‘rigid’ stiffness value in x, y and Z. The Rack link part is connected via ball joints to the two track-rods at the inner ball joint positions.

{bmc bm347.bmp}

+$#>Theory – The Anti Roll Bar Model

Description:

The anti-roll bar added via the default menu adds four new parts, two “Drop Links” and the anti-roll bar itself made up of two separate “Roll Bar Parts”. The two roll bar parts are connected together via a ‘tagged’ point. In compliance this tagged point is treated as a revolute joint being given the defined roll bar stiffness. In total 11 new points are added to the template. The roll bar joint mentioned above, four new C of G points (one for each new part), the two defined attachment points of the drop link to the selected part, the attachment points of the drop link to the roll bar ends, (placed directly above the defined attachment points) and the two roll bar mounts. The roll bar mounts connect the roll bar to ground, (this is the same as the vehicle body). All of the points are solved in post solution forms, (vector pos and Hookes joint), such that no additional equations are added to the kinematic solution. Thus they do not contribute or control the kinematic motion.

{bmc bm348.bmp}

+$#>Theory – The Compliant Hub Model

Description:

The ‘Add compliant hub’ option provides a simple menu selection route to including hub compliance into the existing models template. It adds a new part, the ‘wheel/Hub’ between the upright and ground. Two new points are added one for the new parts C of G position and the other for the connection point. The compliant hub is modelled with a single bush, rather than the more physical two bushes (i.e. the inner and outer bearings), as typical know hub compliance values are usually measured as a single stiffness number. In compliance mode if no bush stiffness values are provided the default ‘Stiff’ values are applied to both axial and rotational stiffnesses. As part of the template modification performed by this option the Wheel centre point and stub axles points properties are changed such that they are associated with the new ‘hub’ part rather than the original ‘upright’ part.

{bmc bm349.bmp}

+$#>Theory – Steering Box Models

Description:

Two optional steering box types are available in the latest version of Shark. By hanging to a ‘steering box’ you do not add any extra parts, you just change how the steering motion is applied to the model. Most importantly the steering motion is no longer assumed to be defined in linear translation of the inner track rod joint (mm), but is now assumed to be the rotation of the steering box about its axis (degrees). The difference between the two is whether the inner track rod ball joint is attached to a common cross rail or the steering arms.

{bmc bm350.bmp}

{bmc bm351.bmp}

+$#>Theory – Leaf Spring Modelling

Leaf Spring Modelling in SHARK

The leaf spring is modelled as a three link component, (rear hanger is ‘fourth’ link). Geometrically the link lengths could be based on the standard SAE1982 definition.

To achieve the required kinematic spring shape with bump travel an adaptive length control element is applied. This senses the change in length between two markers and applies a controlling change in length to the enforced distance between two other markers. In the case of the leaf spring model the control element senses the change in length between the spring rear eye and a point on the axle part and applies a change in length to the distance between the front spring eye and a point on the axle part. The relationship between sensed length and changed length is a user definable look-up table that allows the required kinematic deformed shape to be achieved under bump displacement.

{bmc bm352.bmp}

Because of the solution delay in detect/sense this produces on coarse step size a degree of ‘staircasing’. An alternative approach is available that just uses the z-displacement of a point as the transducer variable, (this will still work with roll). One advantage of this approach is that the stable kinematic solution leads to a better calculation of the roll centre migration.

{bmc bm353.bmp}

The compliant characteristics of the leaf spring are modelled using the bush rotational stiffness and bush pre-loads at the two joint points. Other spring points such as the eye and hanger points are modelled as compliant bushes in the normal way. The limitation of this is that currently the rotational stiffness can only be a linear value, which is limiting when considering multi-leaf springs. The other issue is that the use of the bush pre-load to represent spring loads in the system means that for the as built system, there is no rotations and hence no bush pre-load. Initial pre-loads can’t be defined as non-zero they are only determined by rotation from static build position.

This pre-load issue can be overcome by building the model at some free condition such that the static ride point is at ‘x’ mm of bump travel rather than 0 mm.

+$#>Theory – The Slotted Joint

Modelling a slotted joint in SHARK

The normal steering arm joint used in Shark is the simple ball joint. A modelling option is included, Edit / Convert Ball Joint to Slot that will convert a selected ball joint, (normally the steering arm outer joint) to a slotted joint. This option makes the necessary changes to the template without any further user interaction.

The image below illustrates how the slotted joint makes use of a Hookes’ joint type spider added to the model to act as the connecting part and provide the necessary rotation restriction between the upright and the steering arm. The orientation of the slot can be controlled by the two points ‘Slot Normal1’ and ‘Slot Upper’. The ‘Slot Normal2’ point is defined by a function  that uses the two other axis points to align it and thus is repositioned automatically when you change the ‘Slot Normal1’ point.

{bmc bm354.bmp}

The extra marker point ‘Slot Marker’ is added attached to the steering arm but initially positioned at the same co-ordinates as the ‘slot upper’ point to provide the necessary post processing ball joint rotation targets. To display the joint such that its slot travel can be displayed the parts and markers should be set up as indicated in the figure below.

{bmc bm355.bmp}

A typical display should then look as indicated below for the outer ball joint. With motion being constrained to be linear along the slot direction.

{bmc bm356.bmp}

+$#>KAppendix 1 – Supported Batch Commands

Introduction  

Supported batch commands are given below, grouped by sub-section. The list gives the short string Batch equivalent followed by full menu description and finally any optional arguments. Optional arguments are shown within square brackets []. Menu Items shown in italics are graphical in their action, in that they will require to open a graphical dialogue box to expect some user input and thus should not be used as part of a script file that is required to run completely automatically with no user input. Commands that are switches have an implied toggle if no ‘ON’ or ‘OFF’ is added to the line. Thus in script mode to be certain of a particular switch status always use the ‘ON’ or ‘OFF’ optional argument to ensure required setting.

General Items, (available at all levels)
	QU	Quit Application
	?	List Menus
	/	Up a Menu Level

For use within batch command files and available at all levels;
	!	At the start of the command, identifies it as a comment line
	&	At the end of the command, indicates it to be invisible, i.e. not echoed to screen.
     PAUSE	Causes the batch run to pause and wait for the user to enter an expected value.
		The PAUSE batch command has an optional argument that is used as a prefix to
		the supplied text. Thus additional Batch commands can be placed in front of the 
		users enter values/string to provide an invisible extra command. An example
		might be to ask for a value then add the ED edit command in front of it.

Top Level
	FI	File
	MO	Module
	DA	Data
	ED	Edit
	VI	View
	TR	Tracking
	GR	Graphics
	GP	Graphs
	SO	Solve
	RE	Results
	SE	SetUp
	WI	Window
	HE	Help
	INT	Switch to Interactive Display

File Sub-Menu
	NE	New [Type, End]
	OP	Open [Filename]
	    OP BR	Browser
	    OP DIR	Directory Listing
	    OP CD	Change Directory
	AD	Add End From File… [Filename]
	    AD BR	Browser
	    AD DIR	Directory Listing
	    AD CD	Change Directory
	SA	Save As [Filename]
	    AD BR	Browser
	    AD DIR	Directory Listing
	    AD CD	Change Directory
	DT	Re-Read Default Templates (Skip User)
	UT	Re-Read Default+User Templates
	AC	Add Custom Templates…
	SC	Save Custom Templates (All)…
	EX	Exit
	RU	Run Batch File
	RI	Re-Read <install> INI File
	SI	Save INI File to <install> Folder
	NE	New…
	ET	Edit Templates
	TE	File Text Edit

Module Sub Menu
	2B	2D Bump
	2R	2D Roll
	3B	3D Bump
	3R	3D Roll
	3S	3D Steer
	3C	3D Combined Motion

Data Sub Menu
	PO	Points
	    PO LI	List
	    PO ED	Edit [No./Label X, Y, Z]
	PA	Parameters…
	    PA LI		List
	    PA ED	Edit [Label, Value]
	TY	Tyre Sizes…
	    TY LI		List
	    TY ED	Edit [Label, Value, End]
	SA	Set Static Angles…
	    SA LI		List
	    SA ED	Edit [Label, Value, End]
	TI	Titles…
	    TI LI		List
	    TI ED	Edit [No. String]
	FO	Force Set
	    FO LI	List
	    FO CU	Current [No.]
	UEB	Use Extended Bump Travel [ON/OFF]
	EB	Extended Bump Travel
	    EB LI 	List
	    EB AD	Add [Bump], [Label]
	    EB ED	Edit [No.] or [Label], [Bump], [Label]
	    EB DE	Delete [No.] or [Label] or [All]
	UER	Use Extended Roll Travel [ON/OFF]
	ER	Extended Bump Travel
	    ER LI 	List
	    ER AD	Add [Roll], [Label]
	    ER ED	Edit [No.] or [Label], [Roll], [Label]
	    ER DE	Delete [No.] or [Label] or [All]
	UES	Use Extended Roll Travel [ON/OFF]
	ES	Extended Steer Travel
	    ES LI 	List
	    ES AD	Add [Steer], [Label]
	    ES ED	Edit [No.] or [Label], [Steer], [Label]
	    ES DE	Delete [No.] or [Label] or [All]
	UEC	Use Extended Combined Motion Travel [ON/OFF]
	EC	Extended Combined Mode Travel
	    CM LI 	List
	    CM AD	Add [Steer], [Bump], [Roll]
	    CM ED	Edit [No.], [Steer], [Bump], [Roll]
	    CM DE	Delete [No.] or [All]
	MO 	Model Properties…
	CO	Compliance Data…
	    CO SP	Spring Properties
	        CO SP DI		Display
	        CO SP LI		List
	        CO SP ED		Edit [End, Spring, Parameter, Value]
	    CO DA	Damper Properties
	        CO DA DI		Display
	        CO DA LI		List
	        CO DA ED		Edit [End, Damper, Value]
	    CO DT	Drive Shaft Torques
	        CO DT DI		Display
	        CO DT LI		List
	        CO DT ED		Edit [End, Value]
	    CO BU	Bush Properties (All)
	    CO TY	Tyre Properties
	    CO EX	External Forces
	    CO RO	Roll Bar Properties
	    CO RA	Linear Rack Properties
	    CO NR	Non-Linear Rack Properties
	    CO BS	Bump Stop Properties
	    CO DL	Tyre Properties
	    CO GE	General Data
	MA 	Mass Data…
	VI	View-Edit Coordinates
	EEB	Edit Extended Bump Travel
	EER	Edit Extended Roll Travel
	EES	Edit Extended Steer Travel
	EEC	Edit Extended Combined Motion Travel

Edit Sub Menu
	UN	Undo
	RE	Redo

View Sub Menu
	RE	Refresh
	AU	Autoscale
	FI	Fill Style
	    FI WI		Wire Frame
	    FI FI		Filled
	    FI HI		Hidden Line
	    FI DE	Depth Buffered (Flat shading)
	ST	Std Views
	    ST YZ	y-z
	    ST ZX	z-x
	    ST XY	x-y
	    ST IS	iso
	SE	Set Display Mode Tool…
	CH	Change Units…

Tracking Sub Menu
	TO	Toggle
	AL	All
	X	X
	Y	Y
	Z	Z
	VI	Visible
	LE	Length…

Graphics Sub Menu
	NO	Point Nos
	LA	Point Labels
	LI	Point Limits
	VA	Point Values
	PNO	Part Nos
	PLA	Part Labels
	PCG	Part C of G Visibility
	    PCG PMA	C of G Marker
	    PCG PAP	C of G Axes Points
	    PCG PLX	 C of G Local Axes
	EV	Enhanced Visibility
	    EV SP	Spring
	    EV DA	Damper
	    EV WH	Wheel
	    EV GR	Grid
	    EV BO	Body
	    EV TR	Triad
	    EV OM	Origin Marker
	    EV BG	Body C of G Marker
	    EV MG	Moving Ground/Wheels
	    EV RA	Roll Axis
	DB	Display Both Sides
	CV	Compliance Visability
	    CV BJ	Ball Joints
	    CV BU	Bushes
	    CV TS	Tyre Spring
	    CV BAP	Bush Axis Points
	    CV BLA	Bush Local Axes
	    CV EF	External Forces
	    CV EFA	External Force Axes
	    CV CF	Calculated Forces
	    CV FV	Calc Forces Values
	CC	Copy to Clipboard
	SA 	Save to File… [Filename]
	    SA BR	Browser
	    SA DIR	Directory Listing
	    SA CD	Change Directory
	AV	AVI File Writer…
	DV	View Definition Values

Graphs Sub Menu
	PP	Printer Properties
	AU	Graphs/Autoscale (All)

Solve Sub Menu
	MO	Motion
	    MO GP	Ground Plane
	    MO BO	Body
	CP	3D Compliance
	KI	Kinematic
	EX	External Forces
	SL	Suspension Spring Pre-Load Force
	SR	Suspension Spring Rate
	RB	Suspension Roll Bar Force
	BU	Bush Rotation Pre-Loads
	BL	Suspension Bump Stop Preload
	BR	Suspension Bump Stop Rate
	TV	Suspension Tyre Vertical Rate
	CE	Control Elements
	DL	Drive Shaft Loads
	BK	Braked Hub
	WH	Wheelbase Diff Sol
	    WH FL	Float Wheelbase
	    WH FI	Fix Wheelbase
	GR	Grnd Plane Diff Sol
	    GR TR	Translate
	    GR RO	Roll
	    GR BU	Bump-Rebound
	ST	Solver Tolerances
	    ST LI		List
	    ST ED [Label, Value]		Edit

Results Sub Menu
	FO	Formatted SDF…
	FI 	SDF Spline Fits…
	DA	SDF Spline Data…
	BD	Bush Deflections…
	BR	Joint-Bush Rotations…
	BF	Bush Forces…
	UP	List All Point Coords for User Position…
	AP	List a Point Coords at All Positions…
	AC	List All Point Coords at a Position…
	(All the above have the same set of sub options)
	    LI	List [End No.], [Setup No.]
	    DI	Display [End No.], [Setup No.]
	    WR	Write [Filename]
		WR BR		Browser
		WR DIR	Directory Listing
		WR CD		Change Directory
	    PR	Print [End No.], [Setup No.]
	    SE	Printer Setup…
	    FT	Printer Font Type [0-2]
	    FS	Printer Font Size [1-8]
	RE	Run Report Batch File
	    RU	Run [Filename] or [No.]
	    LI	List Default Files
	    DI	Display [opt Filename]
	    WR	Write
		WR BR		Browser
		WR DIR	Directory Listing
		WR CD		Change Directory
	    PR	Print [opt Filename]

Setup Sub Menu
	PP	Printer Properties…

Window Sub Menu
	VI	View Custom Control Display [No.]
	OP	Open New Custom Control Display…
	PR	Print Custom Control Display [No.]
	PD	Print (to default printer) Custom Control Display [No.]
	PP	Printer Properties…
	CO	Copy to Clipboard [No.]
	SA	Save to File… [No.]. [Filename]

Help Sub Menu
	CO	Contents
	SE	Search for Help On…
	HO	How to Use Hep
	AB	About Lotus Suspension Analysis…

+$#>Appendix 2 – Known Issues and Work Rounds

1) Virtual Memory

Problem: On start up get error message “unable to allocate ****** bytes of virtual memory”
Fix: Modify start up menu/desk top icon to point to “sharknonvc.exe” rather than default “shark.exe” 

2) Garbled Graphics Widgets

Problem: Graphics display appears garbled/partially obscured. In particular this effects selection boxes, for example on the ‘File/New’ dialogue box.
Fix: Associated with small fonts display with high dpi settings. Go to ‘Start / Settings / Control Panel’. Open ‘Display’ settings. Locate the font size, normally under ‘General’ tab. Set font size to small at no higher than 96 dpi. On some user sites this may require local admin rights.

3) Unstable Graphics, No Support for OpenGL depth buffering

Problem: When using the ‘View / Graphics Frame Type / OpenGl’ option, (such that depth buffering is supported), graphics display is unstable and does not properly draw shaded depth buffered view.
Fix: This is associated with the graphics cards hardware acceleration level. To resolve this go to ‘Start / Settings / Control Panel’. Open ‘Display’ settings, select the ‘settings’ tab and select the ‘Advanced’ button. You now need to identify the tab that has the ‘hardware acceleration’ level on. Typically this is under the ‘Troubleshooting’ tab. Try reducing the hardware acceleration away from ‘Full’ towards ‘None’. This is best performed on a step at a time trial basis to test how much of a reduction is required to enable the graphics to perform correctly. On some user sites this may require local admin rights. If it is considered not possible or undesirable to reduce the hardware acceleration level then the user will need to change to the ‘Windows GDI’ graphics frame type, select menu View / Graphics Frame Type / Windows GDI. Users should note that with this graphics frame type, depth buffering/shaded image is not supported.

The introduction at version 4.03i of the ‘Software Double Buffer’ switch see menu View / Use Software Double Buffer should enable all hardware combinations to run in OpenGl mode.

+$#>KKAppendix 3 – Modes of Operation - Flow Diagram

Shark Modes of Operation

Interactive Mode
Shark was originally written to be used as a graphical based interactive multi-window application. In this mode of operation users migrate through the program with mouse based selections of menu and toolbar icon options with data entry into pop-up dialogue boxes and spread sheets.

Command Mode
To support alternative modes of operation required by some users a purely text based command mode has been added. In its simplest form all entry for the command mode is via the keyboard into a simple scrolling text window.

The program can be started in either interactive mode or command mode. The command mode is initiated by the use of the ‘TEXT’ or ‘BATCH’ string added as a passed optional argument from the calling shortcut. It is also possible to switch between modes once the application is open.

With some of the more complex data entry, such as external force sets, it is not possible to edit this information through the simple command line mode. It is however possible to work in a ‘mixed’ mode of operation which although the application may have been started in command mode the more complex data dialogue boxes can still be opened and data entered in the same way as the full interactive method. This mixed mode of operation has one limitation and it is connected with scripted batch running.

Scripted Batch
As mentioned above a sequence of batch commands can be entered into a text file and run as a ‘scripted’ batch mode. If these scripts are intended to be completely ‘hands free’; i.e. no user input, then only text commands should be used. It is anticipated that a number of customer ‘Standard’ script files will be created and placed on the <install> folder to be available to users of all levels. The <install> INI file can be modified to provide on a menu a list of these standard script files, which can then be run simply by a reference number. Also applies to installations that use the <database> folder, they will overwrite any <install> scripts.

Report Script Files
To provide a complete overall automated report generation process, a scripted report file has been introduced. This takes a similar script file approach to the scripted batch mode but is targeted at defining the contents of a report document.

Report script files can produce a complete analysis report that is sent straight to the printer, written/opened to a Word document or displayed in a Rich Text editor. These reports can be a mix of user formatted text, standard results listings and graph displays.

The report script file supports direct text definition, (from single character, single word, single line, to complete external text file), carriage control, (space, new line, new page), batch command, scripted batch file, all standard text reports, user window graphics, visible graph, current graphics or AVI file of current graphics.

As with the scripted batch files it is anticipated that a number of Customer ‘Standard’ report files will be created and placed on the <install> folder to be available to users of all levels. The <install> INI file can be modified to provide via a menu a list of these standard report files, which can then be run simply by a reference number. Also applies to installations that use the <database> folder, they will overwrite any <install> report scripts.

{bmc bm357.bmp}

+$#>Appendix 4 – StartUp Process Order - Flow Diagram

Startup Process – Main Items Identified

Bracketed [--] items are optional / user specific intallation, nos match flow diagram points

Licenses:
(1) Check out License features

Paths:
(2) Set ‘TEMP’ directory to “Temp_Path” or C:\temp,  [ Homedrive/Homepath ]
(3) Set ‘WINDOWS’ directory to “Windir”,   [ Homedrive/Homepath ]
(4) Set ‘STARTUP/INSTALL’ directory to startup directory

INI file headers:
	(5) [ Read top of ‘STARTUP/INSTALL’ INI file ]
	(6) Look for and Read ‘SHARK_DATABASE’ environment variable
	(7) Read top of ‘DATABASE’ INI file (if defined)
	(8) Read top of ‘USER’ INI file from ‘WINDOWS’ folder

Fill internal data values templates etc:
	(9) Fill internal default templates
	(10) Fill templates from ‘STARTUP/INSTALL’_User_Templates.Dat
	(11) Fill templates from ‘DATABASE’_User_Templates.Dat
	(12) Set internal General defaults
	(13) Set internal default solver settings

INI Files:
	(14) [ Read ‘STARTUP/INSTALL’ INI File ]
	(15) Look for and Read ‘SHARK_DATABASE’ environment variable
	(16) Read ‘DATABASE’ INI File (if defined)
	(17) Read ‘USER’ INI file from ‘WINDOWS’ folder

User Language:
	(18) Read ‘_custom.dic’  from ‘STARTUP/INSTALL’, [ from ‘DATABASE’ ]

Command Lines:
	(19) Check for batch or interactive via command arguments

Templates

All corner/axle models created in Shark refer to a particular template number. This number identifies the template that in turn specifies the definition of the model. This includes defining parts, points, graphics, connectivity (bushes) and key points in the template. Individual models map their unique point positions on to the template.

Hard coded into the program (at version 4.03i) are 32 default templates. All of these are available to any user of the software. Some are classed as Rear suspension templates only because they do not have a steerable point identified in them.

For a server installation, on program start up the template file “_User_Template.dat” is searched for in the <install> folder. If it is found any template definitions identified within it are loaded and will either overwrite an existing default template (if the template number is already used by a default entry) or fill an empty slot number.

If a Database Folder is defined, on program start up the template file “_User_Template.dat” is searched for in the <database> folder. If it is found any template definitions identified within it are loaded and will either overwrite an existing loaded template data.

Template definitions can be modified by individual users, thus individuals may have completely different definitions using the same template slot number. To provide a robust definition method, the specific template definition can be optionally included in the models data file. By definition this implies that when a model file is read in it can redefine a template specification, (and also that any subsequent use of the same template number will be similarly affected until the program is restarted or the templates reset).

Extra ‘custom’ templates can be loaded at any time. Custom templates would normally have be a pre-saved set (or single) template, that may be required for occasional use but don’t warrant being added to the automatically loaded “_User_Templates.dat” file.

To allow users to return to a set of known template definitions, menu options are provided that will re-set the template definitions to the hard coded ones only, or the hard coded ones plus the system user templates in the “_User_Templates.dat” file, (if it exists).

{bmc bm358.bmp}
Templates - Flow Diagram

INI File

The INI file contains all the user specific settings. This file is read in each time the program is started. It is updated/overwritten with the current settings when the program performs a normal exit. The program has hard coded defaults for all these settings, which are overwritten by the user settings when the INI file is read. Thus to revert back to the hard coded ‘factory’ defaults a user could delete the INI file prior to opening the application. For the standard installation the INI file is written to the “Windows®” folder (i.e. C:\WINNT), this means that individual users on the same machine could not have their own unique settings. Conversely it also meant that no two machines could expect to be set-up in the same way. An optional INI file is looked for in the <database> folder this is looked for and loaded if found prior to reading looking for the local windows INI file.

For the user specific server installation the INI file process has an additional INI file step on startup. This provides a method that can support both a common setting on all machines and all individual user settings on the same machine. How?

The specific server installation uses a central server for the software install, (i.e. the software is not installed on individual machines). This single location means that an INI file can be placed in this <install> folder that is read by all users. Because this install is seen as a ‘fixed’ file in that it is part of the initial install and then remains unchanged (primarily due to its location) a second system wide INI is required in a more flexible location. This second system wide INI file is to be identified by the <database> location.  This <database> INI file can be modified by an expert user, to set common properties and settings for all users, unlike the <install> INI file which is fixed. Neither of these are written to on program close! But menu options exist to be able to write to them. These become the first two of the three INI files read. The application then looks in the specific user’s directory on the “Homedrive” in the “Homepath” for the users unique INI file. This is the INI file that is overwritten when the user closes the program and thus stores their specific variation of the default server settings. An example of where “Homedrive” and “Homepath” would point to is “C:\Documents and Settings\myusername\shark.ini”. Note that the standard installation uses the ‘Windows’ environment variable for this folder location.

Users can revert back to the system wide server default settings either by deleting their local copy of “shark.ini” prior to opening the application, or once the application is open selecting the menu option “File/Re-Read <install> INI File” or “File/Re-Read <database> INI File”. Note that this three step process will still mean that a users individual settings are still machine specific, but they will start with the same server specific defaults on any other machine. The users could copy their own individual INI file on to a new machine if they wished to preserve all their settings.

{bmc bm359.bmp}
INI File - Flow Diagram

$#>KKKLOTUS ENGINEERING

{bmc bm360.bmp}
{bmc bm361.bmp}
{bmc bm362.bmp}