Skip to content
English
  • There are no suggestions because the search field is empty.

Controller Logging Stopped: Storage or File Transfer?

Identify where measurement files stop progressing and collect useful evidence before changing the controller.

Quick answer: When Q.station measurement files stop arriving, first determine whether the logger is recording to its configured destination or whether completed files are failing to transfer. A successful ping alone does not verify either process. Record the failure time and preserve diagnostic information before changing the configuration or restarting the controller.

Before you start

This procedure is an initial diagnostic checklist for Q.station systems configured in GI.bench. Check the documentation for your controller model, firmware and installed software. It does not establish a cause or recovery procedure for a particular fault.

Work from the current controller configuration. Record observations first and arrange any interruption with the person responsible for the measurement. Do not delete configuration files or databases as a general troubleshooting step.

1. Identify the recording destination

In GI.bench, determine whether the affected logger is under the controller or the project. A project logger records to the computer and requires a stable controller connection and a full GI.bench licence. For a controller logger, inspect the selected variables, logging mode and Storage destination.

For triggered or event-based logging, check whether the configured recording condition occurred. Inspect the configured file length before treating the absence of a completed file as a failure. Follow the data logger configuration guide for the relevant settings.

2. Locate the last confirmed measurement file

Compare the last usable file at the configured recording destination with the last file received at the remote destination. Note each file name, time range and size. Record whether new files are appearing, whether existing files are changing, and whether the storage destination is accessible.

Observation Next investigation
New completed files exist at the recording destination but are absent remotely. Investigate file transfer and the receiving server.
No expected new recording files can be found. Investigate the logger state, recording condition and storage destination.
The recording destination cannot be inspected. Record the access error. File absence remains unconfirmed.

These observations guide the investigation; they do not prove a root cause. Where appropriate, use the guide to accessing logged data. Preserve existing files.

3. Investigate automatic file transfer separately

If the controller sends completed files to a server, inspect the selected connection under FTP Clients and the logger's Send FTP settings. Record the exact error. Name-resolution errors point to hostname or name-server checks; server write errors require checks of the destination path, permissions and storage.

Follow the FTP and SFTP setup and troubleshooting guide. An incoming connection from a computer to the controller is a different direction from the controller sending files to a server; state which operation failed.

4. Collect evidence for technical support

  • Controller model, firmware version and GI.bench version.
  • The affected logger and its configuration, including mode, file length and storage destination.
  • Failure time with time zone, last usable file, exact errors and the observations from the checks above.
  • Whether the issue recurs and which actions have already been taken.

The controller diagnostic procedure explains how to collect system information on a USB drive. Plan for a possible controller restart and measurement interruption before using it. Keep the diagnostic archive for technical support and share it through the agreed support channel.

Frequently asked questions about stopped Q.station logging

Does a successful ping prove that logging is working?

No. Confirm recording and file transfer independently using actual files and diagnostic evidence.

Does a missing remote file prove that the measurement was lost?

No. Check the configured recording destination first. A file-transfer failure and a recording failure require different investigations.

Should I restart the controller immediately?

First record the symptoms and preserve the evidence that is accessible. Agree any restart with the person responsible for the measurement; a restart can interrupt the test and change the fault state.