Q.station Data Logger Guide (GI.bench)

How to configure a Q.station Data Logger with GI.bench

Purpose


This document thoroughly explains how to configure and utilize the logging capabilities of a Q.station (DIN rail mount or Q.brixx version).


Items Required

  • Q.station or Q.station X with adequate power supply
  • PC with GI.bench installed (free configuration version allows full configuration of data loggers)
  • Ethernet cable


Procedure

  1. Assemble hardware (Q.station + measurement modules).

  2. Power on hardware and connect the Ethernet cable between the PC and Q.station.

  3. Start GI.bench.

  4. Open existing project or in a empty project click Read


  5. All controllers on the same network will be displayed, highlight the controller to connect
    to and click OK.


  6. The Q.station and attached measurement modules will be displayed in the project work
    space:


  7. Configure the channels (type, scaling, etc): real and virtual channels.

  8. Under the Q.station section, right-click Data Logging and select Add > Add Logger
    A maximum of (20) loggers can be created in a single Q.station.


  9. Double-click the newly created logger to open its logger settings


  10. Select the data source/databuffer and which channels to save within the logger. Only channels within the selected buffer can be saved within that logger. You can also check the box to automatically use all variables
    1. Logger Name: provide a name for each logger. The data files will include this
      name in the file.
    2. Logger Type: select between continuous, triggered, or event-based.
    3. Logging rate: rate of data collected from buffer. Equal or less than sample rate. (100Hz is max when logging to internal HD)
      Provide a name for the logger, logger type, logging rateFor each logger, select the data source, logger type, logger name, and logger status:

Logger Type: Continuous


With this type, it is possible to select the logging rate of the logger and the size of a single file.


The logging rate can be set in Hz. The size of a single file can be set in seconds, data sets, or bytes:


Logger Type: Triggered

With this type, it is possible to select the logging rate. It is also possible to assign start and stop trigger conditions; the channel(s) must be selected within the same buffer. Pre and/or post-trigger data can also be added.

The logging rate can be set in Hz. The size of a single file can be set in seconds, data sets, or bytes; additionally, the pre and/or post-trigger data can be set in either seconds or data sets.



The possible condition arguments:

  • < : less than
  • <= : less than or equal to
  • > : greater than
  • >= : greater than or equal to
  • == : equal
  • != : not equal


Logger Type: Event-based

With this logging type, it is possible to start logging based on an event. A pre-trigger is optional, while the event length can be specified in seconds, data sets, and bytes. The number of events specifies the size of a single file.

Data Storage

For all 3 logger types, the storage type can be chosen:


Default: automatic drive selection.


This option determines how and in what sequence writing occurs to the
destinations.

  1. The destination for each logger can be chosen next as either the internal memory of the Q.station, SD card, or USB port. The internal memory has a 100Hz logging rate limit.
  2. It is possible to send data to the following destinations: a network drive, an FTP server,
    or via E-mail. How to configure these destinations is explained in separate guides that
    can be found on the Gantner Instruments website:

  3. Make sure to save the settings in the Data Logger Configuration window by clicking the OK button.

  4. Make sure to write any changes to the controller by clicking Write under the configuration tab

  5. After the update, the Q.station starts logging immediately (if continuous is
    selected) or waits for the trigger conditions to occur. Files in the storage destination (i.e.
    USB drive, SD card, etc.) are saved as .dat files and can be opened using GI.bench by uploading history data in the Dashboard section under the Visualization tab