Setting Up Loggers to Record Data to a File

Setting Up Autonomous Data Logging on the Controller

1. Adding a logger to the controller configuration

Right-click the Data logging node under the controller and select Add > Add Logger.

2. Adding variables to a logger

Double-click the newly created logger to open its settings. In the Available Variables tab, select the data source (data stream) and choose which channels to log. Only channels from the selected data stream can be recorded.

3. Setting up the data logger

In the Logger Settings tab, define how data should be recorded. The following parameters can be configured:

• Name: Provide a name for each logger. This name will be used as a prefix for the recorded data files
• Logger type: Choose the logging mode (Continuous, Triggered, or Event-Based) depending on how you want to capture data.
• Rate: Set the rate at which data is recorded to a file. It is possible to set a logging rate that is lower than the actual data acquisition rate, as the data logger will automatically resample the data.
• File length: Define the maximum size of a data file by specifying a limit in terms of time (seconds), number of samples or scanlines (data sets), or file size (bytes).
  
  
  
  When a Triggered or Event-Based logger is selected, an additional Trigger tab appears to configure the logger’s trigger settings.
  

  
  

4. Define file storage settings

In the Storage tab, the file storage parameters can be configured. The following parameters can be configured:

1. Mode: Determines how and in what sequence data is written to different storage destinations. Additional storage destinations can be configured by increasing the Destination count setting.

   1. Move: Data is stored on the primary storage destination. When a secondary storage device is connected, all existing files are copied to it and removed from the primary location, while data storage on the primary destination continues uninterrupted. This allows, for example, transferring files from the controller’s internal drive to a USB drive to free up space.

   2. Copy: Data is stored on the primary destination. When a secondary storage device is connected, all existing files are copied to it while remaining on the primary, with data storage continuing uninterrupted. This allows, for example, retrieving files from the controller’s internal drive via USB while keeping the originals as a backup.

   3. Copy, only new data: Data is stored on the primary destination. When a secondary storage device is connected, any files not yet copied are transferred to it, while storage on the primary destination continues uninterrupted. This allows, for example, retrieving data from the controller’s internal drive using multiple USB drives.

   4. Protected mode: Prevents unauthorized access to data files by blocking unrecognized storage devices. To enable a device to copy files from the primary storage, place an initialization file named !cmd.usr in the root directory, containing:

      1. Section header: [ACCESSDEVICES]

      2. Count: Number of supported devices (e.g., Count=2)

      3. Item entries: Specify one entry for each authorized storage destination (e.g., Item0=Destination1, Item1=Destination2, etc.)

   5. Store to new connected drive: When a second storage destination becomes available, the current file on the primary destination is completed, and subsequent logger files are started on the newly connected storage medium. See the use case example here.

   6. Automatic drive selection: Data is first stored on the primary destination. If it becomes full, logging automatically continues on the next configured destination. If no additional storage is available, the oldest files on the primary destination are overwritten, creating a ring buffer.

2. Destinations can be selected as the Q.station internal memory, network-attached storage, SD card, or USB port (note: Internal memory has a 100 Hz logging rate limit).

3. Optionally enter a name for a subdirectory within the storage destination; it will be created automatically if it does not exist. The subdirectory name supports placeholders, allowing, for example, automatic creation of a new folder each day.

4. File format options and recommended extensions:

   1. UDBF: Native Gantner Instruments binary format (*.dat)

   2. CSV: Configurable ASCII format (*.csv)

   3. MDF: Measurement Data Format, version 4.10 (*.mf4)

   4. FAMOS: Format for FAMOS analysis software (*.dat)

   5. MATLAB: Level 5 MAT file format (*.mat)

5. Control logger storage usage by setting limits on disk space, ensuring efficient management and uninterrupted data logging.
   

   1. Max. files count: Maximum number of files the logger may create (0 = unlimited).

   2. Max. files in dir: Limits the maximum number of files this logger may create in a directory to manage storage space (0 = disabled).

   3. Max. bytes count: Limits the maximum storage size (in bytes) allocated to this logger to manage disk usage (0 = disabled).

   4. Compress files: When enabled logger files are stored in a compressed Gzip (GNU Zip) archive with the “.gz” file extension.

   5. Automatic file deletion: When enabled the oldest files are automatically deleted when the allocated storage space is fully used.

Setting Up PC-Based Data Logging Using GI.bench

GI.bench offers the ability to set up multiple data loggers that can operate in parallel within a single project, recording data directly to the PC.

In the Project Settings of GI.bench, right-click the Data logging node and select Add > Add Logger. Follow the steps described above for a controller logger to configure a project logger.