1. SECTION 13
REQUESTS

2. Requests
This section introduces requests, which are the primary method of output in Adams/Car.

3. Requests What’s in this section: Creating New Requests
Types of Requests
Toggle Request Activity
Show how to create new Requests in the Template builder.

4. Requests Creating New Requests Open template in template builder
Go to Build menu
Point to Request and select New
Show how to create new Requests in the Template builder.

5. Types of Requests
There are three types of requests that you can create
Define Using Type And Markers
Define Using Function Expression
Define Using Subroutine
Show how to create new Requests in the Template builder.

6. Types of Requests
There are three types of requests that you can create
Define Using Type And Markers
You could request four type of outputs such as displacement, velocity, acceleration and force.
You need to specify the markers used for the computation of the output
Define Using Function Expression
You need to explicitly specify the function used in the definition of the request.
You could request any type of outputs by using runtime functions like SFORCE, GFORCE, VZ, VM, DZ, DM, etc.
Show how to create new Requests in the Template builder.

7. Types of Requests Define Using Subroutine
You need to define the request statement as a user-defined request
You could use user defined subroutine to request any type of outputs. In general you could create all types of requests using function expression instead of user subroutine.
You can define requests using the requests number for a subroutine e.g. 905,907
Example:
There is a request named "._double_wishbone.bkl_lca_front.force_request" defined by the User Function shown below :
905.0, 3.0, (._double_wishbone.bkl_lca_front.i_marker[1].adams_id), (._double_wishbone.bkl_lca_front.j_marker[1].adams_id), (._double_wishbone.bkl_lca_front.field.adams_id)
Show how to create new Requests in the Template builder.

8. Types of Requests Define Using Subroutine (Cont.) Where:
905: Request Number
3.0 : is the Force Request (you can have 1.0 and 2.0 as displacement and velocity requests respectively)
Similarly, the remaining components denote the I Marker , J Marker and Field respectively.
Using this request you can obtain the output components e.g. Forces and Torques.
This is how the request appears in the ADM dataset
==================================== adams_view_name='TR_Rear_Suspension_bkl_lca_front_force_request'
REQUEST/94
, FUNCTION = USER (905, 3, 282, 365, 29)
====================================
Show how to create new Requests in the Template builder.

9. Toggle Requests Activity
Toggles the activity of requests in a subsystem or assembly. Any activity change will only be retained during the current session because this setting is not saved in the subsystem (.sub) file.
Types of requests to activate/deactivate include:
actuators
bushings
springs
dampers
bumpstops
reboundstops
all (of the above)
To store the request activity, you should group activity using parameter variables, which are stored in subsystem files.

10. Toggle Request Activity
To store the request activity in Template Builder:
Create a parameter variable to store the activity of the request as a 1 for active, 0 for inactive.
For example, pvs_request_activity.
Create a group with the command language: Tools  Command Navigator. Double click group and select create.
For more information on groups, press F1.
Add your requests to the group.

11. Toggle Request Activity
For the expr_active parameter of the group (1 = active, 0 = inactive), create a function that uses the parameter variable created in Step 1, on the previous slide.
The commands for this might look similar to the following:
For more examples, investigate templates in the shared database which have the group kinematic_mode_active, which is used for the Kinematic Mode toggle.