file rpc read
Allows you to read RPC III files into Adams View.
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 read |
|---|
file_name = | file_name |
rpc_object_name = | dac_file_object_name |
Description:
Parameter | Value Type | Description |
|---|
File_name | String | Specifies the name of the file that is to be read, written, or executed. |
Rpc_object_name | RPC_file_object_name | Specifies the name of the RPC object that is to hold the RPC data. If unspecified, uses the file name. |
Extended Definition:
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.