MMEMory:FORMat:READing:RLIMit

From Keysight 34970A/34972A

MMEMory:FORMat:READing:RLIMit

This functionality is available on the 34972A only.

Syntax

MMEMory:FORMat:READing:RLIMit <row_limit>

MMEMory:FORMat:READing:RLIMit?

Description

This command allows you to specify whether the maximum number of sweeps that can be logged to a single USB data file should be limited to one less than 64K (216 - 1 = 65,535). If <row_limit> is ON, sweeps are stored in files named dat00001.csv, dat00002.csv, dat00003.csv, and so on, with 65,535 sweeps per file. If <row_limit> is OFF, data logged for the scan is stored in a single file named dat00001.csv, which is limited by both the space available on the USB drive and how the drive is formatted, up to a maximum of 232 sweeps (roughly 4.3 billion).

Parameters

Name Type Range of Values Default Value
<row_limit> Boolean {OFF|0|ON|1} This is a required parameter.

The factory default is ON.

Remarks

  • This feature enables you to accommodate certain versions of common spreadsheet, database and data analysis programs that have limitations of 64K rows per file.
  • When the instrument is shipped from the factory, the default state for <row_limit> is ON.
  • The value of the <row_limit> will be saved in non-volatile memory on the instrument and will not be affected by *RST or SYSTem:PRESet.

Return Format

The query returns 0 (OFF) or 1 (ON).

Examples

The following command turns the row limit feature on, causing USB data files to be split at the 64K - 1 boundary.

MMEMory:FORMat:READing:RLIMit ON

 

The following query indicates whether the row limit feature is on. In this case, it is OFF.

MMEMory:FORMat:READing:RLIMit?

Typical Response: 0

See Also

MMEMory Subsystem Introduction

MMEMory:LOG[:ENABle]

MMEMory:FORMat:READing:CSEParator