What Is The Difference Between The AFG3000's TFS And TFW Files?

What Is The Difference Between The AFG3000's TFS And TFW Files?

TFS

This is the setup file for the instrument. It contains information such as function, run mode, amplitude, and offset. It does not contain information such as sample data or GPIB setup. All the instrument attributes affected by recalling a default setup can be saved and recalled via the TFS file. The complete list of these attributes (and default values) is kept in the AFG3000 Programmer Manual in Appendix D.

While it is an ASCII encoded file, creation or modification of a TFS file via third-party applications is unsupported and not recommended.

TFS files are opened from the Recall Menu and files are saved with the Save Menu. The AFG3000 Quick Start User Manual contains more details on the Save Menu and Recall Menu.

TFW

This file contains waveform sample data for one arbitrary function. Unlike oscilloscope waveform files, the TFW file does not contain any amplitude, offset, or timing information. It is raw binary data for the AFG3000's 14-bit DAC and should be thought of as unit less or a ratio. Amplitude, offset, and timing are configured by the operator and applied dynamically. This allows for adjustments without creating a new array of samples. Only when the function shape or ratio between the samples is required will new TFW file be required.

The TFW file uses a proprietary binary format without any official documentation. Like the TFS file, creation or modification of TFW file via third-party applications is unsupported and not generally recommended.

TFW files are loaded from the Arbitrary Waveform Menu or Edit Menu. TFW files are saved from the Edit Menu. The AFG3000 Quick Start User Manual contains more details on the Arbitrary Waveform Menu and Edit Menu.