Preset to Standard and Signal Definition Import/Export (6GR)

These two operations are workflow-linked: Preset to Standard is the reset baseline, and Import Signal Definition layers a specific signal's parameters on top of that baseline. Both are available as buttons on the Signal Config tab's toolbar, and signal-definition import/export is also available from the File menu.

Preset to Standard

Preset to Standard returns the whole measurement to the default 6GR configuration in one click. It is a full re-baseline, not a partial reset:

Every auto-coupled parameter returns to Auto, with its coupled default recomputed (see Auto and Manual Parameter Coupling).
Every collection in the signal configuration (bandwidth parts, PDSCH Physical Downlink Shared Channel/PUSCH allocations, search spaces, CORESETs, SS blocks) is rebuilt to match the default configuration.

Anything you manually overrode is discarded — that is the purpose of the preset. The same operation is available from the menu bar as File > Preset > 6GR Measurement to Standard.

Import and Export Signal Definition (.ksd)

KSD is the PathWave Signal Generation (PWSG) signal-definition file format. A signal engineer building a 6G waveform in PWSG can export a .ksd file describing it, and Import Signal Definition (.ksd)... reconfigures the 6GR measurement to match — carrier, bandwidth part, PDSCH/PUSCH/PDCCH configuration, search space and CORESET layout, and so on — without entering every parameter by hand. Export Signal Definition (.ksd)... does the reverse: it writes the measurement's current signal configuration out as a .ksd file.

An import always starts from the default configuration: the measurement performs the equivalent of Preset to Standard internally before applying the file, so the result depends only on the file, not on whatever the measurement held beforehand. Parameters the file does not specify remain at Auto. Parameters it does specify take the imported values, and become manual settings only where those values differ from what Auto was already producing. See Auto and Manual Parameter Coupling.

The Import Result Summary

A signal-definition file describes more than an analyzer represents, so an import is expected to apply most entries and skip some that have no analyzer-side equivalent. Skipped entries are normal and expected — they do not mean the import failed. After an import, a one-line result summary appears on the Signal Config tab below the toolbar, with the full list of skipped entries and warnings available in a collapsed detail area for troubleshooting.

Import and export are also available programmatically through the .NET API 1) Access Preamble Indicator, or 2) Application Programming Interface (ImportSignalDefinition / ExportSignalDefinition), so the workflow can be scripted.