Adams Basic Package > Adams View > View Command Language > file > file rpc write

file rpc write

Allows you to write out RPC III files from Adams View. This technique does not require you to set up requests before running the simulation.

By definition, results output to an RPC III must have constant time steps. If the results data being output includes non-constant time steps, Adams View issues a warning and the time axis of the data will be warped so that the time interval is constant.

MTS Systems Corporation created the Remote Parameter Control (RPC) III file format. This format has become a standard for writing time history information of loads, forces, and accelerations. With RPC III, you can input data from durability test machines and output data to any RPC III-compatible programs. This topic contains an overview of the RPC III format. For a detailed description of the RPC III format, see www.mts.com.

RPC III files are sequential and fixed-length with 512-byte records. The files begin with a standard header that describes the file contents. The header includes a FORMAT flag that specifies one of four data formats:

■BINARY_IEEE_LITTLE_END - used on Windows systems

■BINARY_IEEE_BIG_END - used on Linux systems

■BINARY - used on VAX systems

■ASCII

Adams View and Adams Durability can read any of the binary formats, so from the point of view of an Adams user, these files are portable between platforms. These products can also write RPC III files in the BINARY_IEEE_LITTLE_END format because MTS only provides RPC III software for the Windows platform.

The RPC III file format supports multi-channel time history data with a fixed sample rate or time step. Adams View and Adams Durability support an unlimited number of channels. These binary files map real data into a short (2-byte) signed integer with the header providing a scaling factor for each channel. Because the scaling factor essentially determines where the decimal point appears in these signed numbers, the maximum resolution of data in an RPC III file is 0.0000305 () when the scaling factor is 1.

A key point to remember is that data that varies less than the magnitude of the channel resolution will not be reflected in an RPC III file. For example, with a scaling factor of 1, changes less than ±0.0000305 will not register in the RPC III data file.

Format:

file rpc write
file_name =	file_name
result_set_component =	existing result_set

Example:

file rpc write &
file_name =	c:\data\rpc_format &
result_set_component =	my_result_set

Description:

Parameter	Value Type	Description
File_name	String	Specifies the name of the file that is to be read, written, or executed.
Result_set_component	Existing result set	Identifies the components of an existing result set. The components must be in an existing result set and reference to the component must include the result set name.

Extended Definition:

1. The proper extension in the file_name parameter is the default, but you can override it by supplying a different extension.

It is not necessary to enclose the file name in quotes if it only contains alphanumeric characters and starts with a letter. If you want to include other characters, such as a '.' for an extension or '/' or '[]' for directory paths, you must enclose the file name in quotes.

2. For example, assume you read a request file named shift.req, and this request file contains the result set REQ1. If you want to refer to the X component in the result set REQ1, enter .SHIFT.REQ1.X (you can omit .SHIFT. if SHIFT is the current analysis_name). SHIFT refers to the analysis name from which the result set came (or is stored under).

Result sets are associated with an analysis and can be identified as such. A result set associated with request 101 from an analysis named test can be referred to as .test.req101.

The table illustrates the default names assigned to result sets and result set components read from request (.req) and results (.res) files.

Result set naming

Result set type:	Result set name:	Component names:	File that result is from:
part	PARxxx...	x y z e1 e2 e3 e4 mag vx vy vz wx wy wz accx accy accz wdx wdy wdz	results file
diff	DIFxxx...	q dq	results file
joint	JOIxxx...	fx fy fz tx ty tz fmag tmag	results file
jprim	JPRxxx...	fx fy fz tx ty tz fmag tmag	results file
motion	MOTxxx...	fx fy fz tx ty tz fmag tmag	results file
gear	GEAxxx...	fx fy fz	results file
coupler	COUxxx...	fx1 fy1 fz1 tx1 ty1 tz1 fmag1 tmag1 fx2 fy2 fz2 tx2 ty2 tz2 fmag2 tmag2 fx3 fy3 fz3 tx3 ty3 tz3 fmag3 tmag3	results file
sforce	SFOxxx...	fx fy fz tx ty tz fmag tmag	results file
spring damp	SPRxxx...	fx fy fz tx ty tz fmag tmag	results file
bushing	BUSxxx...	fx fy fz tx ty tz fmag tmag	results file
beam	BEAxxx...	fx fy fz tx ty tz fmag tmag	results file
field	FIExxx...	fx fy fz tx ty tz fmag tmag	results file
user request	UREQxxx...	u1 u2 u3 u4 u5 u6 u7 u8	results file
request	REQxxx...	x y z r1 r2 r3 mag amag	request file
ucon	(not implemented)